"Restart your computer to install important updates" loop

[Caduceus949]

View attachment 6723

This is fairly fresh install of Windows 7 as of yesterday; I had Windows 8.1 and was getting various errors, so I had to reinstall (not sure if this all points to a pending SSD failure). I've tried the Fix It, I tried the

"fsutil resource setautoreset true %systemdrive%\

attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
del %SystemRoot%\System32\Config\TxR\*

attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
del %SystemRoot%\System32\SMI\Store\Machine\*.blf
del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms"

as given in another thread and it went fine until I got to the TxR portion, where it stated I could not remove some items because they're still in use (same as post #4 in this thread, https://www.sysnative.com/forums/wi...-install-important-updates-infinite-loop.html).

I deleted SoftwareDistribution/Download and /DataStore contents.

I stopped the Windows Update Client and BITS, ran the Fix It, started processes, and rebooted (I watched some youtube videos with possible fixes).

I appreciate anything that can be done, thank you.

Edit-- the CBS folder is attached at the top for some reason. Sorry, I'm new at this.

 

[Tekno Venus]

Hi,

You didn't say you tried this, so can you do the following for me please.

Boot into the recovery environment, and launch command prompt please: How to use the Windows 7 System Recovery Environment Command Prompt

When command prompt is launched, type in the following command and press enter:

DISM /image:C:\ /cleanup-image /revertpendingactions

Then reboot your computer, booting into Windows normally. Run this FixIt in aggressive mode: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

Stephen

 

[Caduceus949]

Please see the attached image, I got an error message and DISM did not seem to complete.

 

[bassfisher6522]

I've had some similar issues with this, having one OS and then moving to another and then back again. Then the clean install was/became buggy. What I did and still do, since it's a relatively new clean install is re-do the clean install. Then making sure that I install all needed drivers for said OS being installed, then I update the OS from MS. For what ever reason this just happens sometimes.