New
#51
Hi Louis,
Just for future reference, you didn't need either of those cd commands.
Well there we have it, Access is denied. I'm still surprised that it failed from the recovery environment - as far as I know, permissions don't apply from there.
Noel suggested to me that it might be because only TrustedInstaller has write access to these files, so I would like to test that theory.
I would like you to download a tool, devxexec.exe, from this link:
Info: DevelopEx Blog » devxexec
Download Link: http://developex.com/downloads/devxexec.exe
Then copy and paste it into C:\Windows\system32
Then open up a Command Prompt as an Administrator and type this command please:
Do not change the directory before running this one!
devxexec.exe /user:TrustedInstaller cmd
If it gives you a warning, click OK, then a new Command Prompt window should open. Close the one that you have just been using, so that you are left with the blank new one, then run this command please:
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Com
ponent Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf38
56ad364e35~amd64~~0.0.0.0" /v "Package_4_for_KB2530548~31bf3856ad364e35~amd64~~6
.1.1.2"
And copy the output as before please.
Tom