Windows update KB 3045999 installed but not installed

mcco · 13 Jul 2015

Hi,

Firstly thanks for your help.

I have a problem with windows update kb3045999. It has caused a lot of problems on my system, with programs not loaded after booting (eg notepad, IE etc return error code The application was unable to start (0xc0000018). I understand that this is a known error and many have posted about it online. I can reboot my computer a number of times and eventually the programmes will work as normal, however that is a bit of a pain.

From reading online it appears the way to fix the problem is to uninstall the update. I thought I had done that but the error kept happening. I then had the idea of reinstalling the update and uninstalling again in-case it did not uninstall correctly, however when I try to install the update it advises me that it is already installed and when I try to uninstall it using the wusa /uninstall command I am advised that the update is not installed.

Any ideas on what to do?

Thanks

Michael

NoelDP · 13 Jul 2015

From your CheckSUR log...

Code:

Checking Component Store
(f)	CSI Missing Deployment Key	0x00000000	a6562cfa922..6d6096de0b7_31bf3856ad364e35_6.1.7601.18846_16108e677bb01de8	HKLM\Components\CanonicalData\Deployments	
(f)	CSI Missing Deployment Key	0x00000000	170aef91da5..bcd5a4992f7_31bf3856ad364e35_6.1.7601.18846_07b81509db0ef196	HKLM\Components\CanonicalData\Deployments	
(f)	CSI Missing Deployment Key	0x00000000	08820e22142..fc0a4cf716f_31bf3856ad364e35_6.1.7601.18846_21db2236a64375c9	HKLM\Components\CanonicalData\Deployments	
(f)	CSI Missing Deployment Key	0x00000000	b6953ce718e..9aa86774558_31bf3856ad364e35_6.1.7601.18846_b7417b0549aa5f1d	HKLM\Components\CanonicalData\Deployments	

Summary:
Seconds executed: 3601
 Found 4 errors
  CSI Missing Deployment Key Total count: 4

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

mcco · 14 Jul 2015

As requested

https://onedrive.live.com/redir?resi...int=file%2czip

Thanks

Michael

NoelDP · 14 Jul 2015

All these 'bad' entries appear to originate from KB3035583.

Have you attempted to use one of the 'hacks' available to either force its install, or disable it?

If not, the best thing is probably to attempt to uninstall KB3035583 from the Installed Updates listing.

If it succeeds, please post a new CheckSUR log, and we'll see if it's done the job.
If it fails, please post the C:\Windows\windowsupdate.log file.

mcco · 14 Jul 2015

Ok done that, here is the log

NoelDP · 14 Jul 2015

- et voila!
CheckSUR is now clean.

Do a Check for Updates, and attempt to install ONLY the oldest update found. If it goes in OK, try the rest.
If it fails, post eh C:\Windows\windowsudpate.log file.

mcco · 14 Jul 2015

Ok, all worked fine for the first update, not for the next one

NoelDP · 14 Jul 2015

I thinks a cleanout of the SoftwareDistribution folder will clear that...
Open an Elevated Command Prompt
Run the following commands
*
NET STOP WUAUSERV
REN C:\WINDOWS\SoftwareDistribution SDOLD
NET START WUAUSERV
*
reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.
*
Install only the oldest update found - and reboot once installed
then go back to Windows updates and install the others.
(You'll lose the Update History in the process, but all updates will remain installed and visible in the Installed Updates listing)

mcco · 14 Jul 2015

I am unable to get this command to work

REN C:\WINDOWS\SoftwareDistribution SDOLD

I don't have a SDOLD folder in C:\windows\Softwaredistrubtion, I do have SDOLD folder in C:\windows

also here is the latest CheckSUR file

NoelDP · 14 Jul 2015

It looks like that last update created even more problems - can you uninstall it?

As far as the above command is concerned - make sure that you get the spacing right
There are TWO spaces....

REN<space>C:\WINDOWS\SoftwareDistribution<space>SDOLD

...and the command must be run from an Elevated Command Prompt.