A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Todays MS update made my Win7 unbootable



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old January 5th 18, 04:48 AM posted to alt.windows7.general
cameo[_3_]
external usenet poster
 
Posts: 1
Default Todays MS update made my Win7 unbootable

There was one critical update pushed from Microsoft today and when the
update finished and was ready for restart, my PC came up with a startup
error from which I could not get out even after booting up with the
Windows DVD in repair mode. Does anybody know what the number was for that
single KB file and did anybody else had this problem?
I tried several prior restore points but that did not work either.
Luckily I also have a Win10 laptop that I am using now, but I really liked
my Win7 PC better.
Unfortunately I don't have any recent system backup file from the
corrupted PC and I can only use individual data file transfers from the
Win7 PC after removing its HD and make it a temp. USB drive for my Win10
laptop.
Ads
  #2  
Old January 8th 18, 01:49 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Solved: Todays MS update made my Win7 unbootable

cameo wrote:


Thanks, Paul. This fix restored my PC to the state it was before this
failed update, but that still leaves the question what to do when the
update shows up again. And it just did this morning with pending
download and install. Luckily my setup does not allow automatic updates
though. Hopefully MS releases a fixed version of this patch, but how do
I know it is a fixed one or the same bad one?
I also read somewhere that this patch might actually need a hardware
and/or firmware fix, too. I just don't see HP or AMD doing it for my old
Pavilion notebook. Anyway, this is what showed up again this morning:

2018-01 Security Monthly Quality Rollup for Windows 7 for x64-based
Systems (KB4056894)

Download size: 231.4 MB

You may need to restart your computer for this update to take effect.

Update type: Important

A security issue has been identified in a Microsoft software product
that could affect your system. You can help protect your system by
installing this update from Microsoft. For a complete listing of the
issues that are included in this update, see the associated Microsoft
Knowledge Base article. After you install this update, you may have to
restart your system.

More information:
http://support.microsoft.com/help/4056894

Help and Support:
http://support.microsoft.com/help/4056894


Now that the machine is upright again, make a backup.

Things I might try:

1) Clean up WinSXS
2) Download the update from catalog.update.microsoft.com and install it.
This is to bypass SoftwareDistribution folder issues, or at least
attempt to do that.

On Windows 8 or Windows 10, the following would be possible
for step (1).

*******
Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
corruption marker is already present in the registry.
It is just a quick way to see if corruption currently
exists, and to inform you if there is corruption. It
does not fix anything or create a log.
This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
It only checks for component store corruption and records
that corruption to the log file.

This is useful for only logging what, if any, corruption
exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
records the corruption to the log file, and FIXES the
image corruption using Windows Update. This should take
around 10-15 minutes up to a few hours to finish depending
on the level of corruption.
*******

However, on Windows 7, DISM is not set up to automatically contact
Microsoft and verify files. While the Windows 8/10 users get to use
DISM, the Windows 7 user needs to download a 300MB+ "CheckSUR" package.

https://support.microsoft.com/en-ca/...date-readiness

(Scroll down until you see...

"For Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008"

A second thing you can look at, is "sfc /scannow", and it checks
what is hardlinked from WinSXS into System32. You need to provide
the command with a file set reference, so you'll have to research
the syntax on Win7. On Win8/Win10, there's a better chance of
automation to help.

After that, when you have a clean bill of health on WinSXS,
try manually installing the borked update using a .msu file
from catalog.update.microsoft.com.

I have to mention these steps, because there's no indication
what's broken, or why it chose your machine to brick. There's
got to be something in the file set on your machine, which is
different from others who got a successful update. If there was
a real problem, it would have showed up on sites like Askwoody.

*******

And actually yes, the radar shows there is trouble for *AMD* users.

Here is a bread crumb, with a series of links to reports of BSOD.

https://www.askwoody.com/2018/multip...up-kb-4056894/

So maybe you should go through the evidence collected there first,
before the "script reader" DISM and SFC steps :-) It's possible
this patch just wasn't tested well enough.

Paul
  #3  
Old January 9th 18, 03:25 AM posted to alt.windows7.general
cameo[_2_]
external usenet poster
 
Posts: 453
Default Solved: Todays MS update made my Win7 unbootable

On 1/7/2018 4:49 PM, Paul wrote:
cameo wrote:


Thanks, Paul. This fix restored my PC to the state it was before this
failed update, but that still leaves the question what to do when the
update shows up again. And it just did this morning with pending
download and install. Luckily my setup does not allow automatic
updates though. Hopefully MS releases a fixed version of this patch,
but how do I know it is a fixed one or the same bad one?
I also read somewhere that this patch might actually need a hardware
and/or firmware fix, too. I just don't see HP or AMD doing it for my
old Pavilion notebook. Anyway, this is what showed up again this morning:

2018-01 Security Monthly Quality Rollup for Windows 7 for x64-based
Systems (KB4056894)

Download size: 231.4 MB

You may need to restart your computer for this update to take effect.

Update type: Important

A security issue has been identified in a Microsoft software product
that could affect your system. You can help protect your system by
installing this update from Microsoft. For a complete listing of the
issues that are included in this update, see the associated Microsoft
Knowledge Base article. After you install this update, you may have to
restart your system.

More information:
http://support.microsoft.com/help/4056894

Help and Support:
http://support.microsoft.com/help/4056894


Now that the machine is upright again, make a backup.

Things I might try:

1) Clean up WinSXS
2) Download the update from catalog.update.microsoft.com and install it.
Â*Â* This is to bypass SoftwareDistribution folder issues, or at least
Â*Â* attempt to do that.

On Windows 8 or Windows 10, the following would be possible
for step (1).

*******
Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* corruption marker is already present in the registry.
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* It is just a quick way to see if corruption currently
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* exists, and to inform you if there is corruption. It
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* does not fix anything or create a log.
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* It only checks for component store corruption and records
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* that corruption to the log file.

Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* This is useful for only logging what, if any, corruption
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* records the corruption to the log file, and FIXES the
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* image corruption using Windows Update. This should take
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* around 10-15 minutes up to a few hours to finish
depending
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* on the level of corruption.
*******

However, on Windows 7, DISM is not set up to automatically contact
Microsoft and verify files. While the Windows 8/10 users get to use
DISM, the Windows 7 user needs to download a 300MB+ "CheckSUR" package.

https://support.microsoft.com/en-ca/...date-readiness


Â*Â* (Scroll down until you see...

Â*Â* "For Windows 7, Windows Vista, Windows Server 2008 R2 or Windows
Server 2008"

A second thing you can look at, is "sfc /scannow", and it checks
what is hardlinked from WinSXS into System32. You need to provide
the command with a file set reference, so you'll have to research
the syntax on Win7. On Win8/Win10, there's a better chance of
automation to help.

After that, when you have a clean bill of health on WinSXS,
try manually installing the borked update using a .msu file
from catalog.update.microsoft.com.

I have to mention these steps, because there's no indication
what's broken, or why it chose your machine to brick. There's
got to be something in the file set on your machine, which is
different from others who got a successful update. If there was
a real problem, it would have showed up on sites like Askwoody.

*******

And actually yes, the radar shows there is trouble for *AMD* users.

Here is a bread crumb, with a series of links to reports of BSOD.

https://www.askwoody.com/2018/multip...up-kb-4056894/


So maybe you should go through the evidence collected there first,
before the "script reader" DISM and SFC steps :-) It's possible
this patch just wasn't tested well enough.

Â*Â* Paul


This is way too much to expect from Windows users to get around a bad
Windows patch. The way I look at it is that it's Microsoft
responsibility to release safe patches in the first place. So I am going
to wait till that happens. I have better things to do with my time than
spend weekends to recover from MS's screw-ups.
  #4  
Old January 9th 18, 11:56 PM posted to alt.windows7.general
Ant[_2_]
external usenet poster
 
Posts: 554
Default Solved: Todays MS update made my Win7 unbootable

cameo wrote:

This is way too much to expect from Windows users to get around a bad
Windows patch. The way I look at it is that it's Microsoft
responsibility to release safe patches in the first place. So I am going
to wait till that happens. I have better things to do with my time than
spend weekends to recover from MS's screw-ups.


Ditto. Newer Windows versions are worse. MS should had never laid off
its QA testers.

--
Quote of the Week: "All good work is done the way ants do things: Little by little." --Lafcadio Hearn
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org
/ /\ /\ \ Please nuke ANT if replying by e-mail privately. If credit-
| |o o| | ing, then please kindly use Ant nickname and URL/link.
\ _ /
( )
  #5  
Old January 10th 18, 02:28 AM posted to alt.windows7.general
Stan Brown
external usenet poster
 
Posts: 2,904
Default Solved: Todays MS update made my Win7 unbootable

On Tue, 09 Jan 2018 16:56:27 -0600, Ant wrote:
Ditto. Newer Windows versions are worse. MS should had never laid off
its QA testers.


They didn't lay them off -- they just outsourced them to unpaid and
unwilling volunteers, like you and me.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://BrownMath.com/
http://OakRoadSystems.com/
Shikata ga nai...
  #6  
Old January 10th 18, 07:38 AM posted to alt.windows7.general
cameo[_2_]
external usenet poster
 
Posts: 453
Default Solved: Todays MS update made my Win7 unbootable

On 1/9/2018 2:56 PM, Ant wrote:
cameo wrote:

This is way too much to expect from Windows users to get around a bad
Windows patch. The way I look at it is that it's Microsoft
responsibility to release safe patches in the first place. So I am going
to wait till that happens. I have better things to do with my time than
spend weekends to recover from MS's screw-ups.


Ditto. Newer Windows versions are worse. MS should had never laid off
its QA testers.


Luckily the package of 8 new patchas they released today no longer
contained that bad one I had trouble with and this package installed fine.
  #7  
Old January 10th 18, 07:39 AM posted to alt.windows7.general
cameo[_2_]
external usenet poster
 
Posts: 453
Default Solved: Todays MS update made my Win7 unbootable

On 1/9/2018 5:28 PM, Stan Brown wrote:
On Tue, 09 Jan 2018 16:56:27 -0600, Ant wrote:
Ditto. Newer Windows versions are worse. MS should had never laid off
its QA testers.


They didn't lay them off -- they just outsourced them to unpaid and
unwilling volunteers, like you and me.


Good one!


  #8  
Old February 2nd 18, 05:24 AM posted to alt.windows7.general
nik buna
external usenet poster
 
Posts: 10
Default Solved: Todays MS update made my Win7 unbootable

cameo wrote:

Luckily the package of 8 new patchas they released today no longer
contained that bad one I had trouble with and this package installed fine.


Can you advise me?
Microsoft update bricked my AMD system this week.
http://al.howardknight.net/msgid.cgi....mixmin.net%3E

Paul kindly referred me to this thread, where I am on Win10 which was
upgraded from Win7 a couple years ago (well, I was on Win10, until the
Microsoft update this week bricked my system).

I'm on an AMD 785G inside an HP Pavilion P6230 with the Aloe motherboard.
Here's what happened immediately after the Microsoft update.
(Nothing works except a safe mode command prompt.)

1. Reset this PC http://i.cubeupload.com/2qpmmt.jpg
2. Scanning & repairing http://i.cubeupload.com/iSgdCX.jpg
3. Startup repair http://i.cubeupload.com/g3waOf.jpg
4. Go back to previous build http://i.cubeupload.com/o5jbt1.jpg
5. Reset thi PC again http://i.cubeupload.com/RTVm65.jpg
6. Reset options http://i.cubeupload.com/BQrRDY.jpg
7. Resetting this PC http://i.cubeupload.com/G6wbuu.jpg
8. There was a problem http://i.cubeupload.com/YLSw2s.jpg
9. Error code 0xc000021a http://i.cubeupload.com/luFNrN.jpg
10. OxFFFFC001CB4CEE50 http://i.cubeupload.com/AIeI0X.jpg
11. Startup settings http://i.cubeupload.com/cN8lpT.jpg
12. I tried every single one http://i.cubeupload.com/Wb4AuW.jpg
13. I tried all attempting repairs http://i.cubeupload.com/dqyHQf.jpg
14. I tried all advanced options http://i.cubeupload.com/pM9fQK.jpg
15. I attached the sata adapter http://i.cubeupload.com/z17IFe.jpg
16. The file system is corrupt http://i.cubeupload.com/lbeTE3.jpg

I don't understand what the error code is trying to say since it's
Microsoft who caused this problem so they should know more than this.
https://docs.microsoft.com/en-us/win...ess-terminated

The only thing that worked was a command prompt to safe mode.
Do you have ideas how I might get my filesystem back after MS bricked it?
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 09:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.