|
|
|
Microsoft botches still more patches in latest Automatic Update
|
|
AfterDawn Addict
|
18. December 2013 @ 13:06 |
Link to this message
|
Botched Black Tuesday patch KB 2887069 freezes, fails to configure, triggers a BSoD, and/or zaps sound drivers
KB 2887069 patch went down the Automatic Update chute last week with an array of problems, but there are workarounds
If you've been trying to install last Tuesday's MS13-101/KB 2887069 patch and are having problems, you aren't alone. It seems that this "important" solution to five separately identified security holes in every version of Windows (and Server and RT) since XP is having all sorts of issues, with the majority reported on Windows 7.
Tell me if you've heard this one before: Almost a week after the patches were pushed to Automatic Update customers, Microsoft hasn't acknowledged the problems, provided a workaround, or said when a fix will be available. The patch is currently being offered to Windows 7 and Windows 8.1 machines.
The SANS Internet Storm Center says there are no known exploits for the patched security holes.
There's a six-page thread on the Microsoft Answers forum that discusses the problems people are having. Depending on how lucky you are, according to the thread, the installer may hang at 7 percent or 12 percent; it may reboot twice, dish up a message that says it "Failed to Configure" followed by a rollback; or it may result in BSoDs. There are also reports in a separate Answers forum thread of messed-up sound drivers: audio output won't work and/or the microphone won't work.
GO HERE TO READ MORE
http://answers.microsoft.com/en-us/wind...4f-f3824f6c1af3
What to do?
If you've been following my years-long tirade about botched Microsoft Automatic Update patches, you know that my first recommendation is to turn off the bloody Automatic Update. Manually check for updates later in the month -- after the masses get used as cannon fodder -- when the coast is clear.
If you're seeing BSoDs and need to get your system back, apparently running System Restore from Safe Mode will make it bootable again. Heaven help ya if you have Windows 8 or 8.1, which are notorious for not creating restore points.
Here's a short list of what you can do if you really, really, really want to get this patch installed:
If you're running AVG, turn it off, install the patch manually, reboot, and turn AVG back on.
Right-click on your C drive, choose Properties, and run Disk Cleanup to clear out your Temp folder. Try installing the patch again.
Uninstall all your Nvidia software -- sound drivers, video drivers, whatever. Manually install the patch. Reboot. Re-install the drivers.
None of those fixes work in every case. Microsoft hasn't figured out what's wrong. I have no idea why it's still offering the patch.
Let's hear it for another botched Automatic Update patch. Somebody tell me how long it's going to take Microsoft to fix its seriously broken patching mechanism. The very least Microsoft could do, as a stopgap, is to implement Patch Mondays. But I won't hold my breath.
t/h SB
This story, "Botched Black Tuesday patch KB 2887069 freezes, fails to configure, triggers a BSoD, and/or zaps sound drivers," was originally published at InfoWorld.com. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest developments in business technology news, follow InfoWorld.com on Twitter.
http://images.infoworld.com/t/microsoft...crosoft_windows
|
|
Advertisement
|
|
|
|
AfterDawn Addict
|
19. December 2013 @ 11:51 |
Link to this message
|
Quote:
"Botched Black Tuesday patch KB 2887069 freezes, fails to configure, triggers a BSoD, and/or zaps sound drivers,"
Here's a short list of what you can do if you really, really, really want to get this patch installed:
If you're running AVG, turn it off, install the patch manually, reboot, and turn AVG back on.
Right-click on your C drive, choose Properties, and run Disk Cleanup to clear out your Temp folder. Try installing the patch again.
Uninstall all your Nvidia software -- sound drivers, video drivers, whatever. Manually install the patch. Reboot. Re-install the drivers.
None of those fixes work in every case. Microsoft hasn't figured out what's wrong. I have no idea why it's still offering the patch.
Guess I?m a ?Lucky Dog?, haven?t had any trouble with MS (Micro-Slug) Updates in several years.
? I always install updates manually.
? Keep my updates set to ?Check for updates but let me choose whether to download and install them?
? Have a daily backup of system drive via Acronis.
? Create a Restore point and Registry backup before installing via Tweaking.com.
? Don?t use AVG.
? Don?t use Nvidia software or drivers.
? Have a Task schedule that runs Ccleaner /auto each hour of the day to clean Temp files.
I do wish Micro-Slug would get their shit together so I wouldn?t have to listen to all the bitching from the customer base? Just kidding. 
There are three kinds of men: The ones that learn by reading; The few who learn by observation;
The rest of them have to pee on the electric fence and find out for themselves... |
Senior Member
|
20. December 2013 @ 01:24 |
Link to this message
|
|
yep,i got mine set to manual as well.if i dont like it i dont install it.thanks so much to Ireland for these heads up.
|
|
jasonbwile
Newbie
|
8. January 2014 @ 23:52 |
Link to this message
|
|
Thanks for these updates. My Windows XP has been running on so slow. I am wincing at the thought of a total reformat if this is to go on for long.
|
|
ddp
Moderator
|
9. January 2014 @ 00:01 |
Link to this message
|
|
jasonbwile, run taskmanager & in processes, see if svchost.exe is running at 50 to 100% while nothing else is running.
|
AfterDawn Addict
|
10. January 2014 @ 14:33 |
Link to this message
|
FIX: When you run Windows Update to scan for updates that use Windows Installer, including Office updates, you may experience a memory leak, or you may receive an error message for the Svchost process
\
Installer, including Office updates, you may experience a memory leak, or you may receive an error message for the Svchost process
When you run Microsoft Windows Update to scan for updates or to apply updates to any applications that use Microsoft Windows Installer (MSI) 3.1 together with Windows Update, you may receive the following error message in Event Viewer on a Windows XP-based computer:
Application popup: svchost.exe - Application Error : The instruction at "0x745f2780" referenced memory at "0x00000070". The memory could not be "read".
Additionally, a memory leak may occur when Windows Update scans for updates that use Windows Installer.
These problems may occur when you try to scan for Microsoft Office updates. You may also experience these problems when you use any one of the following update mechanisms:
go here to read it all
http://support.microsoft.com/kb/916089
This message has been edited since posting. Last time this message was edited on 10. January 2014 @ 14:36
|
AfterDawn Addict
|
10. January 2014 @ 16:09 |
Link to this message
|
|
|
|
ddp
Moderator
|
10. January 2014 @ 16:33 |
Link to this message
|
|
download & run the latest cumlative security update for ie resolves the issue with svchost.exe using so much cpu power.
|
|
Advertisement
|
|
|
AfterDawn Addict
|
11. January 2014 @ 17:12 |
Link to this message
|
Is Windows Update Broken? 5 Broken Updates Microsoft Released In 2013
What happened to Windows Update in 2013? Quality control seems to be suffering as Microsoft scrambles to update their software faster than ever. They?ve released quite a few buggy and broken Windows Updates this year.
Microsoft capped off a year of shaky quality control by releasing a broken firmware update for their Surface Pro 2 hardware and promptly going on vacation, leaving the problem unfixed for over a month. It?s been a rough year.
Surface Pro 2 December Firmware Update
On December 10, 2013, Microsoft released a firmware update for their Surface Pro 2 PC. Microsoft releases such firmware updates on a monthly basis. These firmware updates arrive via Windows Update, so they?re often installed automatically as part of the standard Windows Update process.
The firmware update?s notes indicated that it should fix some problems with battery life and power saving, but it actually did the opposite. Many Surface Pro 2 users began reporting that it dramatically lowered their device?s battery life and broke the sleep function. Because this is a UEFI firmware update ? similar to a BIOS update ? and not a standard driver update, there was no way to uninstall the update and get back to normal.
Microsoft pulled the update on December 18, over a week later. They explained they did so to ?ensure the best experience for our customers during the holiday season.? They said they were ?working to release an alternative update package after the holidays.? Microsoft didn?t want new Surface Pro 2 users to deal with these problems, but they left their existing Surface Pro 2 customers to suffer through the holidays without any form of fix.
They?re now saying that a firmware update will ship on January 14, 2014. That?s over a month from the time the buggy firmware update first shipped. Why the long delay? It looks like Microsoft employees decided to take the holidays off. Some people consider Microsoft?s monthly firmware updates an example of how well-supported Surface hardware is. This incident seems to suggest the opposite ? there?s a reason most PC manufacturers don?t release such frequent firmware updates.
Luckily, for many people, the firmware update just silently failed to install. Bypassing this error requires another complicated workaround involving stopping a Windows service and deleting a system file.
==============================================
Windows 8.1 Gaming Mouse Lag
KB2823324 Causes Blue Screens of Death
KB2803821 Breaks WMV Support, Steam Games
KB2821895 Breaks System File Checker, Causes High CPU Usage
So, Should You Trust Windows Update?
===============================================
GO HERE TO READ IT ALL
http://www.howtogeek.com/179629/is-wind...leased-in-2013/
|
|
