Home > Uncategorized > Windows update failing, use dism to uninstall the failing package

Windows update failing, use dism to uninstall the failing package

After reviewing the c:\windows\system32\cbs\CBS.log and c:\windows\Windowsupdate.log, the following failure was reported in the windowsupdate.log file:

2016-08-29	10:26:05:812	 984	11c0	Agent	Attempt 1 to obtain post-reboot results.
2016-08-29	10:26:06:999	 984	11c0	Handler	Post-reboot status for package Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4: 0x80004005.
2016-08-29	10:26:06:999	 984	11c0	Handler	WARNING: Got extended error: "Generic Command	ErrorCode	80004005	Executable	bfsvc.exe	ExitCode	112	Phase	38	Mode	Install (upgrade)	Component	Microsoft-Windows-BootEnvironment-Core-BootManager-PCAT, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS"
2016-08-29	10:26:11:812	4304	58c	COMAPI	-----------  COMAPI: IUpdateServiceManager::RemoveService  -----------
2016-08-29	10:26:11:812	4304	58c	COMAPI	  - ServiceId = {6d7dbb69-4bc2-4e6e-9dec-0651152c5691}
2016-08-29	10:26:11:874	4304	58c	COMAPI	IUpdateService removing volatile scan package service, serviceID = {6D7DBB69-4BC2-4E6E-9DEC-0651152C5691}
2016-08-29	10:26:11:874	 984	cb8	Agent	WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
2016-08-29	10:26:11:953	4304	58c	COMAPI	WARNING: ISusInternal::RemoveService failed, hr=80248014
2016-08-29	10:26:12:015	 984	a88	Report	REPORT EVENT: {0D6E181E-8A07-40B9-BD04-93B81A786626}	2016-08-29 10:26:07:015-0400	1	182	101	{5A44EA4D-9446-49BC-AB5F-71C9A8FE21B4}	501	80004005	wusa	Failure	Content Install	Installation Failure: Windows failed to install the following update with error 0x80004005: Update for Windows (KB3125574).
2016-08-29	10:26:12:015	 984	a88	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-08-29	10:26:12:015	 984	a88	Report	WER Report sent: 7.6.7601.23453 0x80004005(0x17766a8) A44EA4D-9446-49BC-AB5F-71C9A8FE21B4 Install 501 0 wusa {21586AC6-9DBE-4916-8E8C-F6B5F901AF52} 0

Try running the following then reboot, then try to reinstall the failing package:

dism.exe /online /remove-package /packagename:Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4

You might note that the failing KB is one of these new fangled cumulative rollups which contains a bunch o’ packages. Even after a roll back by the Windows updates client, I was surprised to see that this package was still installed. Meaning the above dism command didn’t return an error, but succeeded.

However, in my specific case, the following was found in the CBS.log file:

2016-08-29 12:10:38, Info                  CSI    00000369 Calling generic command executable (sequence 75 (0x0000004b)): [20]"C:\Windows\bfsvc.exe"
    CmdLine: [47]""C:\Windows\bfsvc.exe" C:\Windows\boot /nofonts"
2016-08-29 12:11:10, Error      [0x018009] CSI    0000036a (F) Done with generic command 75 (0x0000004b); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 112 (0x00000070) resulted in success? FALSE
    Process output: [l:8995 [4096]"BFSVC: BfspCopyFile(C:\Windows\boot\PCAT\bootmgr, \\?\GLOBALROOT\Device\HarddiskVolume1\Boot\bootmgr) failed! (Attempt 1 of 60) Last Error = 0x70

This indicates that HarddiskVolume1 has not enough room (error 112, try running `net helpmsg 112`). HarddiskVolume1 is the System Reserved Partition. This is fairly convoluted, but you must add a drive letter to the partition, give a user ownership, take full control, then you can manage the files, remove the drive letter, reboot and try to install the hotfix again. And always remember to drop the size of a file to 1KB, hit it with the old `echo > file.ext`.
 

ref: http://answers.microsoft.com/en-us/windows/forum/all/windows-update-fatal-error-c0000022/95545731-a30d-4672-aca5-55d254a9efd1?auth=1

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: