• 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**

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
BTW - all those updates are listed in blue at the top of the Windows folder. Use Explorer and click on each. It will show you specifically what files were updated - mostly DLLs. There were 8 of these on Tuesday, 13 Feb. And . . . those same files can be used to uninstall any particular update.
 
Updated today with no problems.

Had a nasty series of BSODs with games but it turns out it was my memory/board @1000MHz. Backed it down to 800MHz and sailing along again.
 
Originally posted by: mechBgon
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.
Click to expand...

Where do you read that I patched 11,000 machines?
 
It is a problem. Does anyone know that if you chose 'use last good config' and were able to boot, if you'll still have problems after further shutdowns?

Also, what drivers on a P5W DH Deluxe would this have overridden that I'd need to possibly reload?
 
Originally posted by: Pale Rider
Originally posted by: mechBgon
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.
Click to expand...

Where do you read that I patched 11,000 machines?
Click to expand...
Since you stated "We lost a cluster of Exchange servers today due to this," it appeared that you were referring to your domain. Do you have any stats on how many of your 11,000 systems at work actually were affected?

 
Originally posted by: corkyg
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. ???
Click to expand...


And we have a winner!!! 😉

Serves me right for just checking all the box's on the update page without really thinking about what I was doing ... "if it ain't broke, don't fix it" def applies here!

What actually happened was that my wifes LJ-1012 is identified as a LJ-1010 by the default HP driver & installed that way it plays nice with the A516 photo printer, however for some reason when the driver update correctly ID'ed it as a LJ-1012, the A516 took possesion of USB printing, regardless of changes made to port settings or even adding new ports manually & it was time-consuming to fix.
 
Did you install the optional driver updates as well? One of my co-workers did that, and hosed his system too. Pressing F8 when booting and going back to the prior working configuration fixed it, though. He got lucky.

I'm sure that most ATOT'ers know this already, but you should NEVER get drivers from Windows Update. Go directly to the manufacturer whenever possible.
 
Originally posted by: Pale Rider
We lost a cluster of Exchange servers today due to this. We thought it was the San unit at first.
Click to expand...

No you lost a cluster of exchange servers because the group responsible for patching those servers failed in their due diligence and did not properly test the updates before rolling them out.

Still sounds as if it is windows update doing driver updates. I never allow windows update to touch my drivers. I never allow WU to do anything without my permission first.
 
I have not heard any word of issues here. Just received the distributed workstation patch on my lappie (already on this desktop). That will be around 30-40k by Wednesday. No news on the server side either and they should have finished testing on Friday.

Must be one of those "special" custom configs by the Exchange server folks. Probably have a one-off image/install process. The only update issues we have had directly involved installation shortcuts the support/dev groups made on their own (changing ACPI registry key types from REG_BINARY to REG_SZ; making NT system drives >8GB).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top