Unable to install KB4532693 in v1909 Errorcode 0x8007010b

Topic

New Reply

KB4532693 does not install here on a Thinkpad X220 i7 with Windows 10 1909. Errorcode 0x8007010b. Its predecessor KB4532695 had the same issue. It installs, but when rebooting it stops at 7% complete, says it could not complete the update and continues with undoing the changes and reboots once again.

This happens with the automatic installation and also on a manual installation, using the Update Catalog.

All other updates for this patch Tuesday installed flawlessly.

sfc /scannow reports no problems
The Windows Update troubleshooter does not even detect there is an issue with Windows Update and cannot find a resolution

I already cleaned the update logs with diskclean and the update cache by renaming Software Distribution and Catroot2.

System:
Lenovo X220
Intel Core i7 2520M
Microsoft Windows [Version 10.0.18363.592]
Windows Defender with all updates (todays definitions installed without problem)

Thanks in advance for any hints.

1 user thanked author for this post.

yabutey

Reply | Quote

Replies

Consider running the Windows Update Troubleshooter:
https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Jan-E

Reply | Quote

OK, try a couple of other things. You should’t be logged in with a Standard User account.  You can copy/paste the commands one at a time. Record any errors or failures and post back here.

If you have a HDD (not SSD) in an elevated command prompt run
chkdsk /f
Reboot when asked.

In an eleveted command prompt:
dism /online /Cleanup-Image /RevertPendingActions
dism /online /cleanup-image /restorehealth
sfc /scannow
Try to update again.
If it is unsuccessful, run the Windows Update Troubleshooter in Settings\Update and Security under Troubleshooter.

1 user thanked author for this post.

Jan-E

Reply | Quote

[Jan-E]

Thanks a lot for both replies!

Hoever, no luck. It is a 1TB SSD with a lot of partitions. I already did a fsutil dirty check on all partitions

C:\>fsutil dirty query c:
Volume – c: is NOT Dirty

The followed your advice:

C:\>dism /online /Cleanup-Image /RevertPendingActions

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

Reverting pending actions from the image…
The operation completed. Revert of pending actions will be attempted after the reboot.
The operation completed successfully.
Restart Windows to complete this operation.
Do you want to restart the computer now? (Y/N)

Rebooted. After the reboot I tried it once again:

C:\>dism /online /Cleanup-Image /RevertPendingActions

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

Reverting pending actions from the image…

Error: 0x800f082f

An error occurred reverting the pending actions from the image.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Installed KB4532693 and rebooted. At the reboot it still stopped at 7% complete and rebooted with undoing changes.

Ran the Windows Update Troubleshooter. Both versions: The installed one and the online one recommended by @geekdon. No issues found, no reso;ution found.

• This reply was modified 5 years, 3 months ago by Jan-E. Reason: code changed into blockquote

Reply | Quote

[Jan-E]

Ouch. When I changed the code BBcodes into blockquote my reply vanished. I will try it once again.

Edit: and after posting this repply it appeared again.

• This reply was modified 5 years, 3 months ago by Jan-E.

Reply | Quote

Jan-E, the forum anti-spam captured your post due to editing and submitting it too quickly.
Give it at least 5-6 mins before editing/submitting next time

Windows - commercial by definition and now function...

Reply | Quote

OK, I’m going to grab at straws:
Verify you have last month’s SSU KB4528759 installed. It won’t be listed in Update History. You will have to look in Installed updates.
Do you have this Feb. SSU KB4538674 installed? If not, try downloading it and manually installing it. Did that work?

And considering Woody’s latead blogpost, maybe you should just wait on the install of the CU. His article will be out shortly in ComputerWorld. And we are still on DEFCON-2.

1 user thanked author for this post.

Jan-E

Reply | Quote

I tried reinstalling KB4528759 from the update catalog: “Security Update for Windows (KB4528759) is already installed on this computer.”

The same with the other one: “Security Update for Windows (KB4538674) is already installed on this computer.”

Reply | Quote

Of course, I could wait. No other option at the moment. But I had the same problem with the optional KB4532695. Which is more or less the predecessor of KB4532693, although it has a higher KB number.

Reply | Quote

When and what was your last valid cumulative update?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Jan-E

Reply | Quote

Jan-E wrote:

Microsoft Windows [Version 10.0.18363.592]

That’s Jan Patch Tues. update.

2 users thanked author for this post.

Jan-E, geekdom

Reply | Quote

The Windows 10 partition is fairly new. I moved the Windows 7 partition to my other SSD and made a clean install of Windows 10 between January 6 and January 10 this year. I must have installed the January CU around January 15, but cannot know for sure because I cleaned the update logs & cache.

In the second half of January I only got KB4532695, so the January CU was installed.

Reply | Quote

If you look in Installed Updates you will find that information. It is not cleared by cleaning the update logs and cache.
Windows Update\View update history – link to uninstall updates on the upper left.
OR
Control Panel\Windows Update – View installed updates link on the upper left.

If you had installed KB4532695, your Build would be 18383.628 instead of .592

1 user thanked author for this post.

Jan-E

Reply | Quote

Optional KB4532695 Build 18383.628 was a non-Security optional install update issued 1/28.
KB4528760 (indicated by your Build 18383.592) was a Security update issued on Jan Patch Tues.

I’d still wait a while and let’s see what develops.

1 user thanked author for this post.

Jan-E

Reply | Quote

Maybe you were just lucky. See this post about Feb. CUs. That’s what DEFCON is for.

Reply | Quote

Oops.

FWIW: while I was testing this on my ‘production’ laptop, I did the same update on a X220 i5 (my previous laptop) that is functioning as a backup now. No issues with icons. And also no issues with KB4532693. The update installed smoothly.

Reply | Quote

And this from my Insider FAST Ring information known problems:

We’re investigating reports that some Insiders are unable to update to newer builds with error 0x8007042b.

Reply | Quote

Another errorcode. Of course I googled for 0x8007010b. I found a few references to invalid directories like here:
https://www.hresult.info/FACILITY_WIN32/0x8007010B

Needle, haystack.

Reply | Quote

I had this problem and spent hours following all the suggestions, reboots & watching windows updating as far as 1 – 2% before system restart, only to be informed that it hadn’t been installed & was reverting to its previous state. Finally solved it by re-installing (updating, not clean install) Windows 1909 update via the 1909 Windows update .iso. After it had completed, listed in the installed updates was the elusive KB4532693. It took about 45 minutes, much less than the time I spent tracking down and actioning the various solutions offered on multiple websites. Bit of a nuclear solution, but it worked for me.

1 user thanked author for this post.

Jan-E

Reply | Quote

Did you have the same error message?

I am thinking of the same solution. I will start with making a clone of my Win 10 boot partition, in order to have a way to recover if needed.

FWIW: I also had a bare Win 10 in a Virtualbox. I gave one shortcut a custom icon vefore updating. No problems.

Reply | Quote

It was exactly the same error message and update number. Its an old system, non-uefi, Core2 Q9650 quad, but its updating ok now.  I have 2 Core i5 9600k uefi systems, a couple of AMD  FX systems (uefi)  & a laptop (also Core2-non-uefi), all had no problems with this particular update. Good luck…

1 user thanked author for this post.

Jan-E

Reply | Quote

In my case it is the other way around. The UEFI i7 system with a fresh Win 10 boot partition (SSD) has problems. The older non-UEFI i5 system with an older Win 10 boot partition (HDD) had no problems whatsoever.

1 user thanked author for this post.

yabutey

Reply | Quote

Also meant to say, after the process of re-updating  had completed, I noticed a fresh recovery partition had been inserted, between the W10 partition and the old recovery partition. I used a partition manager to move & recover the space used by the old partition, about 500mb. (System reboots & updates ok now) It did make me wonder if the old recovery partition was corrupt and/or was in someway responsible for the update error? I do wish Microsoft would come up with more specific clues as to why an update failed in real time, instead of a broadly defined error code.

 

Reply | Quote

Same here, our machine that runs our intranet on iis. Decided to just do a reinstall

Reply | Quote