[SOLVED] W11 21H2 -> 22H2 0x8007001f

Anderkor

Anderkor

New member
Joined
Sep 22, 2022
Posts
3
Hi!

I'm using Gigabyte Aero 15X V8. It's a laptop compatible with Windows 11. I'm trying to install 22H2 update on 22000.978. It's appeared in Windows Update center. I've tried:
1. Reset winstore (not sure it's relevant).
2. Reset Windows Update cache (disabling services, renaming folders, starting services).
3. SFC and DISM.
4. Install using ISO (keeping files).
5. Install using ISO and suspending BitLocker (repair install).
6. Install using assistant.
7. Tried running SFCFix (without user-specific files provided on this forum, of course) - it hasn't found issues.

Every attempt results in 0x8007001f. Also in events I've found 0x80242016 error also related to Windows Update, but I haven't found specific fix for it (I mean different from what I've tried).

Despite this 21H2 was a clean installed, I had never experienced such issues upgrading this laptop to different Windows 10 versions.

Thanks for your time and answers in advance.
 

Attachments

What was the result of DISM and SFC? I assume that they both ran to completion with no errors?

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB5017024 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Hi x BlueRobot!

Yes, you're right. Sorry, I meant to write that it run without errors.
Today I've tried to update again (thought that there may be a patch or something released to fix this), but faced this error again. After research (just ~30 minutes before your reply), I found files called setupact.log and setuperr.log, analyzed them and found the problem: I had two users with similar name - one of them was deleted, but still appeared in registry. Once I've deleted it from ProfileList (and some other references), update's been completed successfully.
Anyway, thanks for your answer, I do really appreciate your attention.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top