Trying to update to Windows11 22h2 but always fails even when trying to install fresh ISO

Anonymous

I've been trying to update to the latest Win11pro 22h2 since last December. Not working well at all. It always gets to 98% and then "something happened" and it rolls it back to 21h2 as you see below. I've tried everything except to nuke the SDD and treat it like is was a new unit. Not really wanting to go that route.

I started just with the Windows update, no joy.

moved to the ISO, mounted and install, no joy.

turned off my Antivirus and tried above two methods again, no joy.

uninstalled my Antivirus and tired above two methods again, no joy.

I've been reading these forums and trying their ideas, no joy.

need a little help here I guess to move forward. I've pasted my machine info below and there are links to SETUPACT.log, SETUPAPI.LOG, and a screen shot of the error after a reboot from trying to install from ISO and it did its automatic roll back.

SETUPACT.log: https://1drv.ms/u/s!ApNnd0WJC5zahVcJuecXbkgIqPYG?e=NJ3zEk

SETUPAPI.LOG https://1drv.ms/u/s!ApNnd0WJC5zahVaWIlWpf14BL4l-?e=PWShbz

screen shot: https://1drv.ms/b/s!ApNnd0WJC5zahVnCV9ccg2DCKH4d?e=2iqg8J

Device name JOES-DESKTOP-072019

Full device name

Processor AMD Ryzen 5 2600 Six-Core Processor 3.85 GHz

Installed RAM 32.0 GB

Device ID 0201820E-6Bxx-47E5-9B71-xxxxxxx456F4

Product ID

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro

Version 21H2

Installed on ‎1/‎17/‎2022

OS build 22000.1281

Experience Windows Feature Experience Pack 1000.22000.1281.0

Any help is appreciated,

JoeF

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

44 answers

Ramesh 181.9K Reputation points Volunteer Moderator

2023-02-14T17:56:50+00:00
Please uninstall VirtualBox. And then do the following:

Backup your device drivers using DISM or PnpUtil, as mentioned here. It's a quick and easy procedure.

Once done, from an admin Command Prompt, run these commands:
- pnputil /delete-driver oem25.inf /uninstall /force
- pnputil /delete-driver oem79.inf /uninstall /force
- pnputil /delete-driver oem80.inf /uninstall /force
- pnputil /delete-driver oem76.inf /uninstall /force
- pnputil /delete-driver oem73.inf /uninstall /force
- pnputil /delete-driver oem77.inf /uninstall /force
- pnputil /delete-driver oem10.inf /uninstall /force
Upload a screenshot of the output window.

See if you're able to update Windows now. If an error appears, run SetupDiag and upload the fresh set of logs (or the Logs.zip package.)
Was this answer helpful?

0 comments No comments
Anonymous

2023-02-14T18:30:57+00:00

Just to add a little more to what has been mentioned.

Your Bios version is from 2018, perhaps a newer one is available.

This is showing and may be related to the vBox. There seems to be a problem related to OEM9.inf (oemwin2k.inf) and oem57.inf (tap0901.inf). The OEM9.inf (oemwin2k.inf) is a 2012 file and is replaced by oem57.inf. Probably not related to the upgrade failure.

And then there are these. The same file but different versions, although it doesn't appear to be related to the upgrade problem.

SP Attempting to remove unused drivers

Info SP Searching for unused drivers that may be removed from the system.

Info SP Drivers will be removed during this pass.

Info SP INF oem40.inf (ntprint.inf_x86_3159bf8e7aa3738b) will be removed.

Info SP Import Date: 2022/10/12 08:46:11:684.

Info SP Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

Error SP Failed to remove INF oem40.inf, Err = 0x3[gle=0x00000003]

Info SP INF oem64.inf (ntprint.inf_x86_4ed8db010e3eb220) will be removed.

Info SP Import Date: 2022/10/27 12:54:59:178.

Info SP Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

Error SP Failed to remove INF oem64.inf, Err = 0x3[gle=0x00000003]

Info SP INF oem39.inf (ntprint.inf_x86_828c30be6a2db3e0) will be removed.

Info SP Import Date: 2022/08/10 15:52:59:543.

Info SP Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

Error SP Failed to remove INF oem39.inf, Err = 0x3[gle=0x00000003]

Info SP INF oem58.inf (ntprint.inf_x86_b51896fb6cf04317) will be removed.

Info SP Import Date: 2022/09/22 13:52:45:228.

Info SP Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

Error SP Failed to remove INF oem58.inf, Err = 0x3[gle=0x00000003]

Info SP INF oem68.inf (ntprint.inf_x86_9b34e890200daa97) will be removed.

Info SP Import Date: 2022/11/19 10:52:13:284.

Info SP Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

Error SP Failed to remove INF oem68.inf, Err = 0x3[gle=0x00000003]

Info SP Driver packages removed: 0
Was this answer helpful?

0 comments No comments
Anonymous

2023-02-14T19:07:31+00:00

ok, VBox uninstalled.

drivers backed up...

command lines ran (except the last one failed).

going to try Win update through the system now and we'll see.
Was this answer helpful?

0 comments No comments
Anonymous

2023-02-14T19:39:32+00:00

The "system update" failed.

I checked the setupact.log file in the \panther\ folder and it has the same modified time and date as well as file size as the one I posted a link to above from 9:48 this morning. ????

Don't know if I'm getting the proper file there.

Saltgrass:

thanks for that post, for kicks, I have deleted those four (4) drivers as well, then rebooted my computer.

I'm now going to try an install from the OS version.... again....

ps. I'm logged in with my laptop to this forum now so I can monitor while we let the smoke out of my desktop....
Was this answer helpful?

0 comments No comments
Anonymous

2023-02-14T20:57:58+00:00

No Bios updates found?
Was this answer helpful?

0 comments No comments