talksr Posted March 6, 2014 Author Posted March 6, 2014 you need to call wusa to install an msu. Are you able to give me an example call so I know what to put?
talksr Posted March 6, 2014 Author Posted March 6, 2014 Ah wusa Windows6.1-KB947821-v32-x64.msu has done the trick. It is running now, lets see what happens.
talksr Posted March 6, 2014 Author Posted March 6, 2014 Running as administrator on cmd, it starts to run installer and then I get: Windows Update Standalone Installer Installer encountered an error: 0x80070005 Access is denied! FLAMING NIGHTMARE!
psydii Posted March 6, 2014 Posted March 6, 2014 psexec, vista and .msu files - Sysinternals Forums (v busy, so being v brief) 1
Arthur Posted March 6, 2014 Posted March 6, 2014 Running as administrator on cmd, it starts to run installer and then I get I usually find it easier to open a Command Prompt as Administrator, run psexec -s -i -d cmd.exe to open a second Command Prompt as SYSTEM, then run the installer from there. i.e. wusa.exe D:\Windows6.1-KB947821-v32-x64.msu 1
talksr Posted April 3, 2014 Author Posted April 3, 2014 (edited) I usually find it easier to open a Command Prompt as Administrator, run psexec -s -i -d cmd.exe to open a second Command Prompt as SYSTEM, then run the installer from there. i.e. wusa.exe D:\Windows6.1-KB947821-v32-x64.msu Hi, thanks for your post. I have done exactly what you said, and I get the following message: Windows Update Standalone Installer Only one instance of wusa.exe is allowed to run. If I kill wusa.exe on Process Manager, and re-run, I get the following error: Windows Update Standalone Installer Installer encountered an error: 0x80070002 The system cannot find the file specified. Edited April 3, 2014 by talksr
talksr Posted April 3, 2014 Author Posted April 3, 2014 After bouncing the server and trying again, I now get the following error: Windows Update Standalone Installer Installer encountered an error: 0x80070005 Access is denied.
talksr Posted April 8, 2014 Author Posted April 8, 2014 Hi there, does anyone else have any further thoughts or suggestions?
psydii Posted April 8, 2014 Posted April 8, 2014 (edited) My pervious advice stands: call microsoft, get it fixed and move on to other matters. Make sure you frame it as 'windows updates not working' rather than the specific error code.. I hear that sometimes they can be a bit literal about what constitutes the end of the case. Edited April 8, 2014 by psydii
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now