• 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 7 users urged to uninstall broken update that wreaks havoc on software

From the article

haacknl04
By the way, there was an update released this morning (KB3024777) that fixes the issues with KB3004394 so don't all get your panties in a bunch. To all the people saying they "couldn't update their driver) how many times in the last 48 hours have to really needed to do that, or how many updates have been released in the last 48 hours for your graphics card that were crucial to your computer. I'm guessing none. Further, would anyone really have noticed a difference if they would have waited until today and just installed the fix this morning? People read the article, then freak out... I bet you think your PC has Ebola too....
Click to expand...
 
It broke plenty of things that have nothing to do with driver updates.

Anything trying to use PlayReady DRM wouldn't function for example. This means no TV tuning via media center. The Zune app was broken, etc.
 
It's funny too because all it is stated to do is uninstall the other update. Also, on the windows update page, the selected box is grayed out, so you can't choose not to uninstall this one (like you would want to).

What? Do I faintly hear the sound of someone getting axed in the distance?
.
.
.
.
.
Doubt it, we all make mistakes.
 
I had an issue recently with two windows 7 pc's and when I looked it was Norton 360 that was going crazy on both of them. Needless to say I uninstalled Norton however on my laptop it got worse and I ended up doing a clean install to clear things up. Afterwards I came into two copies of 8.1 pro x64 through my university so I'm off windows 7 now.
 
Not sure if this is related, but want to share my headache and maybe help someone else... I'm running two Windows 7 Pro x64 installs on very different hardware, but both running a Nvidia 560ti.

I started getting this error on shutdown and restarts: cmd.exe failed to start. Everything appeared to be running ok, so after the normal pd of memtest86+, disk drive diagnostics, BIOS update on one of the machines.....I finally so eff it and reinstalled Windows 7 on one of hte systems. The error was gone, until I ran the full install of Nvidia's graphic driver.

Geforce Experience is the source of hte conflict, but probably has to do with this particular windows update, since this problem only appeared recently.

msconfig > startup > uncheck Geforce Experience - error gone. I'll enable it in a couple weeks and see if the error cleared.
 
ch33zw1z said:
Not sure if this is related, but want to share my headache and maybe help someone else... I'm running two Windows 7 Pro x64 installs on very different hardware, but both running a Nvidia 560ti.

I started getting this error on shutdown and restarts: cmd.exe failed to start. Everything appeared to be running ok, so after the normal pd of memtest86+, disk drive diagnostics, BIOS update on one of the machines.....I finally so eff it and reinstalled Windows 7 on one of hte systems. The error was gone, until I ran the full install of Nvidia's graphic driver.

Geforce Experience is the source of hte conflict, but probably has to do with this particular windows update, since this problem only appeared recently.

msconfig > startup > uncheck Geforce Experience - error gone. I'll enable it in a couple weeks and see if the error cleared.
Click to expand...

If you think this update is to blame, uninstall it. If you don't have this update, the error is elsewhere. Moreover, why would cmd.exe not start? Can you launch the command prompt manually?
 
RampantAndroid said:
If you think this update is to blame, uninstall it. If you don't have this update, the error is elsewhere. Moreover, why would cmd.exe not start? Can you launch the command prompt manually?
Click to expand...

cmd.exe works just fine. nothing seems to be wrong. just on shutdown or restart this error pops up: cmd.exe application error 0xc0000142
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top