Windows 7 won't start after update on 5 Jan 2018

Hello everyone, I just registered to share the solution I found.
This morning the same thing happened at work and I found this thread. I tried torchwood's solution without success, because my version of Windows was 32 bits.
I've solved this by listing recent updates to the computer and removing that particular one (in my case it was changing "x64" to "x32").
Execute the command (Replace path-to-mount-directory with the character of your case, mine was D):

Code:

dism /image:path-to-mount-directory /get-packages >installed_updates.txt

Once finished, open the file installed_updates.txt and find the line containing the update we are looking for. I found it searching by date (05/01/2018). Copy the name of the update and now execute torchwood's steps. I did it without scratchdir.

Code:

dism /image:path-to-mount-directory:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24002.1.4(or whatever you copied) /norestart

once it's finished, restart and you should start right away. I have disabled windows update until I know there is a solution.

I hope that it will help you. Greetings.

So this 'fix' still does not install the 1/18 security update? It just makes the computer work? I always manage my own updates and never let windoze automatically do it, I've got limited BW. My version of W7 fixed itself after the BSOD 2 times and it also deleted that update. That's when I started looking around.

BTW what are these 'optional Security and Quality Rollups....' that I never install? Why do an optional one when I can wait for the real monthly one? Plus I don't want that W10 thing showing up on my tray.

If anyone has the knowledge, it would be interesting for them to trace it and see what the offending instruction is that causes the crash. Strange it is happening on the Amd Cpu's - or so it seems.

Repair disc command prompt with
DISM /image:X:\ /cleanup-image /revertpendingactions (X being the drive letter assigned to your boot drive)
worked for me to get it booting again.


Credits to WakeXT

Getting a bit interesting now:

https://www.cnbc.com/2018/01/09/micr...cs-freeze.html

When I started this morning (1-09) that update was still listed, but I didn't install. I just checked a minute ago and it's gone. I guess they'll come out with a replacement?