• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

**WINDOWS UPDATE WARNING**

HannibalX

HannibalX

Diamond Member
So far I have SIX machines that after installing the updates from MS that came out this week that will not boot. They are in a boot loop.

Three systems are part of a corporate network.

Two more systems are part of a completely different corporate network.

The last machine is my personal machine.

I have experienced failures on two machines which I scratch loaded today. They have zero days on the OS, literally from install to updates to failure.

So far I have not been able to find a solution for the loop.
 
Originally posted by: Pale Rider
So far I have SIX machines that after installing the updates from MS that came out this week that will not boot. They are in a boot loop.

So far I have not been able to find a solution for the loop.
Click to expand...

This may seem stupidly obvious, but what about hitting F8 before Windows starts to load and rolling back to the "Last Known Good Configuration?" Assuming you haven't tried it, that should restore the system to the pre-update state.

I'm just suggesting that because I had to use it on a couple of Dells that were stuck in a boot loop (not due to Windows updates, though).
 
I had a similar problem, but because I used F8 to boot from another drive soon after, I thought I had screwed up. No problems after I selected the correct HD.
 
I have updated mine with those new updates and I haven't encountered a single issue since then.

Maybe that those six machines are all un-stable for various reasons other than MS's updates.
 
Originally posted by: MercenaryForHire
I've got <counts> around 6000 systems in Active Directory that say you're wrong.

- M4H
Click to expand...

I have 11,000 machines in my AD. What does my e-penis have to do with this?

Friendly warning that?s all.

I specifically stated information about the machines to the effect that they are not similar machines - meaning not a coincidence. If you haven't had problems, great! MS has acknowledged to me over the phone that they know about the issue.
 
IME corporations with >5000 desktops tend to have more than one Windows admin. Are you sure you guys aren't 1 of like 20 lan admins?

anyways pale, I think 6 out of 11,000 sounds like good odds for a known (admittedly very bad) issue. Have you heard whether it affect any of the server updates, I get to update Exchange server this weekend
 
Originally posted by: Moose1309
IME corporations with >5000 desktops tend to have more than one Windows admin. Are you sure you guys aren't 1 of like 20 lan admins?

anyways pale, I think 6 out of 11,000 sounds like good odds for a known (admittedly very bad) issue. Have you heard whether it affect any of the server updates, I get to update Exchange server this weekend
Click to expand...

We actually have a team of people who do patching throughout the enterprise, thats all they do it make sure all our machines are patched for the OS and all our applications.
 
Originally posted by: DLeRium
Since when do people patch automatically from M$? Especially in a corporate environment.... IT needs to okay platches before they go through..
Click to expand...

Yup - thats why we DIDN'T patch and my test machines and servers died. The people who patched our Exchange servers are part of a different division - which is run by morons.
 
sweet... thats why i have a beta group running on vms and clone machines before releasing to the desktop team... ill give it a shot and see if its affecting my beta group...
 
Happened to me, thought it was my config. had to f8. Any suggestions on ways to make sure I don't get screwed when I turn this thing off again? Do I need to do a backup, revert a setting (windows restore is disabled), or save anything to a cd?
 
The two PC's I run on a daily basis both had all updates with no trouble at all, as did both my kids PC's however my wifes (figures, huh? 😛 ) PC had major problems when I updated it Weds night. It didn't fail to boot or anything, but it did have an issue caused by an optional HP driver for her Laserjet 1012 printer she uses for work.. she also has an HP A516 photo printer hooked up to the same PC & after the update was applied it became the only printer on the system.. the LJ1012 was disabled & couldn't be made to work by anything short of removing every scrap of HP software from her computer, manually editing the registry & re-installing both printers from the original driver CD's.


 
IMO, a problem rate of 6 failures out of ~11,000 systems is not a sufficient reason to advise people en masse not to install their Critical security updates.
 
I think this is more of an isolated error...I just updated my pc with the new patches and everything works fine.
 
Originally posted by: Lord Evermore
At least not without figuring out which update caused the problem and warning against that one.
Click to expand...


If anyone has an HP LJ-1012 (or similar) & any model HP photo printer or inkjet installed on the same system, I strongly suggest that you don't install any print-driver updates, either from Windows update or from HP directly.
 
I have two desktops and a laptop. All were auto-updated this week, and there are no problems. There are two HP printers in the loop - no problems there.

I don't recall any printer driver updates in the package. All printers work perfectly - so there really is no reason to update them. ???
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top