blogsasebo.blogg.se - Only one instance of wusa.exe windows 8.1

ONLY ONE INSTANCE OF WUSA.EXE WINDOWS 8.1 INSTALL
ONLY ONE INSTANCE OF WUSA.EXE WINDOWS 8.1 UPDATE

ONLY ONE INSTANCE OF WUSA.EXE WINDOWS 8.1 INSTALL

So I decided to use the "dism.exe" command to install the CAB file included within the MSU file.

ONLY ONE INSTANCE OF WUSA.EXE WINDOWS 8.1 UPDATE

Operating system package-servicing commands (DISM) can be used offline to install, remove, or update Windows® packages provided as cabinet (.cab) or Windows Update Stand-alone Installer (.msu) files. You see, DISM can be used to install CAB files as well. So I decided to go a slightly different way. But I wanted one method to rule them all. In the cases where it did not work I received a strange error. It worked on the Windows Language packs, but not on IE 11 nor the hotfixes. However, for some reason, this command did not work on all packages. The solution is to install the MSU files by using the command DISM.exe /Add-Package. In the Microsoft article mentioned in the previous paragraph a potential solution is presented. Mind you, the installation itself worked fine, but it took a really long time to complete. After 25 minutes or so it (probably) ended in a time-out. In the end, the WUSA.exe process simply "got stuck" for whatever reason. Either the WUSA.exe tried to contact servers on the Internet (which it could not) or it tried to find some information on the local Windows Update servers which it could not find. It does have sufficient rights to contact the Windows Update server in the LAN, but not to contact Windows Update servers on the Internet.Īs I said, I am not 100% sure what caused the delay in the process.

This account has very limited permissions outside of the local server.

Secondly, the SCCM installation runs under the local System account.

To me this means that the WUSA process tries to contact either the Windows Update server within our LAN or it tries to reach a Windows Update server on the Internet. This is the first step in the installation process. msu file to search for applicable updates".

First of all, as written in the aforementioned Microsoft article, the WUSA.exe " uses the Windows Update metadata in the.

In the end, I suspect the problem has to do with two things: I have to admit that I am still not 100% sure why the problem arose, but the main cause is for sure related to how the process WUSA.exe works. msu file name extension is associated with the Windows Update Standalone Installer. The Windows Update Standalone Installer uses the Windows Update Agent API to install update packages. The wusa.exe file is located in the %windir%\System32 folder. The WUSA.exe is the Windows Update Standalone Installer. In my installation packages I used the WUSA.exe to install the software. Since I was creating a new golden image for my XenDesktop 7.x workers and I was installing 8 language packs this took about 2 hours! This was unacceptable of course. For example, an Internet Explorer language pack took up to 25 minutes to install, which under normal circumstances should only take 2 minutes or so. The installation of the individual installations took a REALLY long time. The PowerShell wrapper was started by SCCM, which means that it runs under the local System account. Wusa.exe %InstallFile% /quiet /norestart /log: %LogFile%

Execution script: PowerShell (version 5.0).

System deployment tool: Microsoft SCCM 2012 R2.

Operating system: Windows Server 2008 R2.The Situationįirst of all let's be clear under which circumstances my problem arose: Then use the following command to install the software:ĭism.exe /online /add-package /packagepath:"%InstallFile%.cab" /quiet /norestart /logpath:"%LogFile%"ĭism.exe /online /add-package /packagepath:"C:\Temp\Windows6.1- KB2896256-圆4.cab" /quiet /norestart /logpath:"C:\Logs \Install_hotfix_ Windows6.1-KB2896256-圆4.log"įor more information please continue reading.Use the following command to extract the MSU file:Įxpand -f:* "C:\%InstallFile%.msu" %TEMP%Įxpand -f:* "C :\Temp\ Windows6.1-KB2896256-圆4.msu" C:\TEMP Do not use the MSU file to install the software, but instead, extract the MSU file and use the included CAB file instead (not the one called WSUSSCAN.cab, the other one).In case you are in a hurry and are not waiting for any blabla, here is the quick version of the solution: