[SOLVED] Win10-22H2 Security Update(KB5027215) installs to 90+% and "rolls back": System is a Win10-22H2-OSbuild 19045.2913

[Gary R]

To be safe I'd make a full image backup to detachable media.

We're editing a registry element that associates directly with a driver, upon which a number of other drivers rely.

It's not that there's a high risk of things going wrong, but in a potentially unstable machine (and because of the updating problems you're having we have to assume yours could be) then if they did then it's conceivable that your machine could become unbootable.

 

[Jay11]

@Gary R please find process below "fixlog" attached... continuing to the next...

• Start FRST.
• Hit your Windows Key + R to open a Run window
• Type Notepad then click OK
• This will open an empty Notepad document
• Copy/Paste the following into it (Don't include the word Code: ) .....

Code:
cmd: sc stop fvevol
cmd: sc config fvevol start= disabled
cmd: sc stop iorate
cmd: sc config iorate start= disabled
cmd: sc stop rdyboost
cmd: sc config rdyboost start= disabled
cmd: sc stop volsnap
cmd: sc config volsnap start= disabled

• Save it as fixlist.txt to the same location as FRST (must be in this location)
• NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
• Now press the Fix button once and wait.
• FRST will process fixlist.txt
• When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
• Please post me the log

 

[Jay11]

@Gary R after restart 2nd procedure run... "fixlog" attached... continuing to 2nd reboot.

Code:
cmd: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f} /v LowerFilters /t REG_MULTI_SZ /d fvevol\0iorate\0rdyboost /f
cmd: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f} /v UpperFilters /t REG_MULTI_SZ /d volsnap /f
cmd: sc config fvevol start=boot
cmd: sc config iorate start=boot
cmd: sc config rdyboost start=boot
cmd: scconfig volsnap start=boot
cmd: sc start fvevol
cmd: sc start iorate
cmd: sc start rdyboost
cmd: sc start volsnap

 

[Jay11]

@Gary R Yeah, the "_inaccessible boot device_" BSOD is what I was greeted with after the 2nd procedure. Thanks for "encouraging" me to do a backup. I restored and I'm back up and running. System back to the state prior to running both procedures.

 

[Gary R]

OK, the problem was caused by a missing space in one of the code lines in post #79 which meant that a critical driver (volsnap.sys) did not start at bootup. My most humble apologies for not spotting it before I posted.

========= scconfig volsnap start=boot =========

'scconfig' is not recognized as an internal or external command,
operable program or batch file.

Should have been ...

sc config volsnap start=boot

I've corrected post #79 now, so can you please try the fix posted in post ... Win10-22H2 Security Update(KB5027215) installs to 90+% and "rolls back": System is a Win10-22H2-OSbuild 19045.2913 ... again.

 

[Jay11]

@Gary R shoo... shows just how important backups are when we do these kind of things (LOL). :) Thanks for not "breaking" my system completely.
Will get to it hopefully tomorrow — Gotta do some work now. Thanks for your perseverance.

 

[Gary R]

Yes, backups are a lifesaver. Once again I apologise for the mistake in the script, I'll proof read more closely in future.

 

[Jay11]

@Gary R Procedure #1 (Proc1) done. Fixlog attached. Rebooting now...

 

[Jay11]

@Gary R Procedure #2 (Proc2) done. Fixlog attached. Rebooting now...

 

[Jay11]

@Gary R I'm back... Reboot #2 proceeded successfully. I'm logged in

I'll await your further feedback.

 

[Gary R]

OK, please try updating.

If successful, please let me know.

If not, please post your latest CBS.log

 

[Jay11]

@Gary R OK, finally managed to get around to running the Windows 10 Update.

Before I tell you the result, I just wanna mention that I noticed a higher than normal CPU usage in PC idle mode, BEFORE STARTING THE WIN UPDATE, as well as very high power usage from the Intel Rapid Storage Technology (IRST) service in the task manager. I decided, after some research, to disable this service in "Services" and I then did a system reboot.
After the reboot the Intel Rapid Storage Technology (IRST) service didn't start and I proceeded to run the Windows update and HOORAY, success, after almost 1hr of running during the reboot process. After login another update followed, didn't take as long as the first (3 update packages) and the system restarted and no issues so far. Windows update is reporting "Up To Date".

Would like to hear your thoughts on... Do you think that I should keep the Intel Rapid Storage Technology (IRST) service disabled/remove it, OR would you suggest use it/start it?

Thanks so much for your help :)

 

[Gary R]

Glad to hear that you're now able to update.

This has been an interesting problem, with a number of contradictory symptoms, that confused things, and some errors that I haven't come across before. Thanks for sticking with it.

My thanks also to ... Maxstar ... and ... x BlueRobot ... for their invaluable assistance in helping to resolve things.

The information I've found for Intel® Rapid Storage Technology ...

Intel® Rapid Storage Technology Driver Installation Software with Intel® Optane™ Memory (10th and 11th Gen Platforms)

Says ...

Note: Intel recommends that end users utilize driver updates provided by their system manufacturer/provider or via Windows* Update to eliminate the potential impact caused by loading non-customized drivers. System manufacturers regularly customize Intel generic drivers to meet the needs of their specific system design. In such cases, use of the Intel generic driver update is not recommended.

... so could be that you have a version of the Intel Rapid Storage Technology that may not be configured correctly for your machine. Hard to say, it's outside my area of expertise.

What I suggest you do is leave it diabled for the present, and see whether that causes any problems. If any occur you can always re-enable it. I would not remove it though.

 

[Jay11]

@Gary R Thank you for sticking with it as well. It was an interesting journey for me as well (I def. learned a few things).
Re. Intel Rapid Storage Technology (IRST) service — will do

And thank you to your team of support as well... Maxstar ... and ... x BlueRobot ... Thank you for the interesting journey of learning and growing knowledge.

Have an awesome weekend ALL!!

 

[Gary R]

You're welcome, glad we could help.

I'll mark this topic as solved.