Windows 10: 10130 update error 0x80d02002, any solutions?

Hi all. I am dual booting 10 and 7 on a Dell XPS 12 with 500GB SSD and 8GB RAM. No problems generally. Only issue is that I cannot get build 10130 to install. Plenty of free space, all other updates are working fine. Have left it a couple of days, including multiple reboots, have also run "dism.exe /online /cleanup-image /restorehealth". The thing that has me confused is that I ran a test install on a spare 256GB SSD, and it updated to 10130 without issue. Every other variable apart from the dual boot on the 500GB is the same.

So does anyone have any insight into the cause, and how to fix it? Have spent a few hours trawling google but not found anything specific or helpful.

Thanks

:)

 

Feature update to Windows 10, version 1709 - Error 0x80d02002

Feature update to Windows 10, version 1709 - Error 0x80d02002

Update keeps failing

 

windows update

How To Fix Windows 10 Update Error 0x80072ee2 and 0x80d02002

 

If you're swaping hard drives, try re-seating the drive and make sure the cables are snug.

Check the disk for errors (probably not, but...)

If you have the other drive connected ... disconnect that one, leaving only the 500 GB drive connected.
Launch an elevated Command prompt and enter the following commands
(*** are comments, not part of the command set)

Diskpart

sel dis 0
*** assuming the 500 GB is the only drive in the box.
*** Otherwise select the drive you will clean

clean
*** erases first and last 100 mb - no data is accessible after command runs - it's fairly quick

exit
*** exit diskpart

exit
*** exit command prompt
Over on Microsoft community, this was marked as the answer that helped in previous builds
Method 1 essentially resets Windows Update

 

Thanks Slarty. Method 2 seems to have worked, I just went into settings, then time and language, then added English UK language. Worked after that, am at 52% of 10130 now. Much appreciated.

 

That's great - glad you got it sorted out.

 

Method 1 worked for me. *Smile

 

would not install for me tried always for two days how time flys in the end reinstalled 9926 then after a couple of minor updates it found the upgrade took over two hours me thinks they best get their act together or hope none reads these forums b4 launch day

 

Excellent, a two-for-one post. It's great that you were able to get around the issue.

 

There are many reports on the forums about things not working. Win10 is after all pre-release code and that's the purpose of the Technical Preview - to help identity issues before Win10 is officially released.

It sounds as though you were able to bring your system up-to-date - it was a pin sure, but it worked. There isn't much information about the particular reasons you had to install 9926, usually just installing the previous ISO (slow ring release) is enough.

Good trouble shooting to find a solution that worked on your machine - I'm glad you were successful.