Get Rid of The Windows Update and Service Pack Installation Blues
(3 votes, average: 3.67 out of 5)
Loading ...
May 11th, 2011 written by Tibor in Windows Insights
Windows Update is an important part of Microsoft’s operating systems. Unfortunately, it’s also one of the more fragile Windows components—update issues are among the most common problems that plague users. And this can be dangerous—without some updates, you may be open to security vulnerabilities! Windows Update just can’t be ignored, so in this week’s blog post, we compiled several troubleshooting tips to help you get this feature back on its feet when it fails.
The images above are just four examples of what can go wrong when you update your PC. This guide will help you if:
- Windows Update no longer starts
- Multiple Windows Updates cannot be installed
- Cryptic error codes appear during updates
- Service Packs and/or individual update or hotfix packages cannot be installed
What’s causing the Windows Update issues?
Updating your Windows machine involves replacing hundreds of files, and the process depends on dozens of built-in Windows components such as System Restore, cryptography features, digital signatures, the Windows Update service, Windows installers, drivers and group policy settings—the list goes on and on. Windows Update and Service Pack installations will fail if one of these components is defective, disabled or not set up properly.
1. Use Microsoft’s Fix It Solution (for Windows XP, Vista, Windows 7)
Microsoft is well aware of the issues surrounding its update feature and provided a tool designed to help fix several dozen issues at once. For example, the tool correctly sets up the cryptographic service, re-registers broken file associations, cleans up the Windows Update catalog folder and repairs important files related to Windows Update.
Click here to download Microsoft’s Fix It Solution. Run the tool then restart your machine afterwards.
2. Install the latest “System Update Readiness Tool” (for Windows Vista, Windows 7)
A bug in Windows (specifically the servicing store) may prevent you from installing future Windows Updates or Service Packs. Microsoft released the “System Update Readiness Tool” to allow users to immediately repair these issues—this will help if our first tip didn’t work. Use the following links to download this feature:
Windows 7 (32-bit), Windows 7 (64-bit), D Windows Vista (32-bit) and Windows Vista (64-bit).
3. Run TuneUp Utilities 2011′s troubleshooting wizard
If your Windows Update asks for a restart each time you launch it, TuneUp Utilities 2011 has a solution for you. Our suite features a handful of troubleshooting wizards that solve common Windows problems like this issue. Just install the product (you can download a 15-day trial), go to the “Fix Problems” category and launch the “Fix common problems” wizard. Check “Windows Update does not work, since a previous restart is required”, and hit “Next”.
4. If all else fails…
Microsoft has a huge Knowledge Base topic covering 11 methods for repairing Windows Update—the first five discuss the company’s Fix It Solution, while the others require some nifty workarounds that are explained in detail. We also advise you to temporarily disable your antivirus solution or firewall in order to proceed with the update, but don’t forget to re-enable them after the update is complete.
Is Windows Update or any of the Service Pack installations giving you trouble? Did our solutions work out for you? Let us know!
May 14, 2011 at 5:55 pm
Windows update was turned off by HP support. It appears that the problem I am having is occuring with other HP users also.
The last two automatic updates failed to install and when I shut the HP Laptop down it downloads the two updates. When I reboot the installations fail and much time is consumed in both operations. This keeps happening unless I turn off Windows update. HP will be consulting with Microsoft to come up with a solution. If you have any knowledge about this situation I would appreciate knowing about it; I have informed HP that I use TuneUp Utilities and am very satisfied with the product.
May 15, 2011 at 12:27 pm
Joseph, thanks for your comment! We haven’t heard about these issues and a google search didn’t really help. This seems like a serious problem – is there an official statement from HP regarding this issue? Would love to find out what the problem is and share it with other readers of this blog!
Best, Sandro
May 19, 2011 at 7:47 pm
Sandro,
I have not heard back from HP support as of now.
I did fool around with, “Microsoft Fix It,” and
somehow have accidentally solved the problem.
I am very disappointed with my paid for
HP support and other paid for support such
as, Linksys,(Cisco.) There is probably a
space for an independent online support group
that would do a good job. Think about it.
Thank you for your help.
Joe Popolow
May 23, 2011 at 5:10 pm
Hi Joseph – thanks for giving me a heads-up on this. Good to hear that Fix It solved the problem!
If you paid for your support privilege, then you should definitely file a complaint.
Best wishes, Sandro
May 30, 2011 at 2:00 am
Don’t know what’s happening. A. Jones
May 30, 2011 at 12:09 pm
Hi Arthur, problems with Windows Update or SP1?
Best, Sandro
June 22, 2011 at 4:01 pm
Please help, I have tried to solve this Java problem. No success!
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0xb5e850c8, pid=4644, tid=4720
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode, sharing windows-x86 )
# Problematic frame:
# C 0xb5e850c8
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
————— T H R E A D —————
Current thread (0x04eb0c00): JavaThread “AWT-Windows” daemon [_thread_in_native, id=4720, stack(0x05570000,0x055c0000)]
siginfo: ExceptionCode=0xc0000005, reading address 0xb5e850c8
Registers:
EAX=0x6d0c01b2, EBX=0×00000001, ECX=0x0716a7a8, EDX=0×00000004
ESP=0x055bf9c0, EBP=0x055bf9ec, ESI=0x04eb0d28, EDI=0x0716a7a8
EIP=0xb5e850c8, EFLAGS=0×00010293
Top of Stack: (sp=0x055bf9c0)
0x055bf9c0: 6d09cb90 00000000 6d09c650 00000000
0x055bf9d0: 055bfa68 00000000 04eb0d28 055bf9c4
0x055bf9e0: 055bfa80 6d0c04a8 00000001 055bfa18
0x055bf9f0: 74cd62fa 00030596 0000981a 0716a7a8
0x055bfa00: 00000000 6d09c650 dcbaabcd 00000000
0x055bfa10: 00000000 6d09c650 055bfa90 74cd6d3a
0x055bfa20: 6d09c650 00030596 0000981a 0716a7a8
0x055bfa30: 00000000 4b96a2a1 055bfb24 055bfb1c
Instructions: (pc=0xb5e850c8)
0xb5e850a8:
[error occurred during error reporting (printing registers, top of stack, instructions near pc), id 0xc0000005]
Register to memory mapping:
EAX=0x6d0c01b2 is an unknown value
EBX=0×00000001 is an unknown value
ECX=0x0716a7a8 is an unknown value
EDX=0×00000004 is an unknown value
ESP=0x055bf9c0 is pointing into the stack for thread: 0x04eb0c00
EBP=0x055bf9ec is pointing into the stack for thread: 0x04eb0c00
ESI=0x04eb0d28 is an unknown value
EDI=0x0716a7a8 is an unknown value
Stack: [0x05570000,0x055c0000], sp=0x055bf9c0, free space=318k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C 0xb5e850c8
C [USER32.dll+0x162fa] gapfnScSendMessage+0×332
C [USER32.dll+0x16d3a] GetThreadDesktop+0xd7
C [USER32.dll+0x177c4] CharPrevW+0×138
C [USER32.dll+0x1788a] DispatchMessageW+0xf
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j sun.awt.windows.WToolkit.eventLoop()V+0
j sun.awt.windows.WToolkit.run()V+52
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
————— P R O C E S S —————
Java Threads: ( => current thread )
0x04ebbc00 JavaThread “Thread-38″ [_thread_blocked, id=4964, stack(0x065d0000,0x06620000)]
0x04eba400 JavaThread “Timer-2″ [_thread_blocked, id=3200, stack(0x063b0000,0x06400000)]
0x04ebcc00 JavaThread “Thread-21″ [_thread_in_native, id=2600, stack(0x07790000,0x077e0000)]
0x04ebc400 JavaThread “Thread-20″ [_thread_blocked, id=4756, stack(0x07700000,0x07750000)]
0x04ebb000 JavaThread “Thread-13″ [_thread_blocked, id=1556, stack(0x06580000,0x065d0000)]
0x04eb7800 JavaThread “thread applet-etrade.mcaster.Streamer-1″ [_thread_blocked, id=3732, stack(0x058b0000,0x05900000)]
0x04eba000 JavaThread “AWT-EventQueue-2″ [_thread_in_native, id=3068, stack(0x05600000,0x05650000)]
0x04eb9800 JavaThread “Browser Side Object Cleanup Thread” [_thread_blocked, id=3644, stack(0x06360000,0x063b0000)]
0x04eb8c00 JavaThread “Windows Tray Icon Thread” [_thread_in_native, id=4796, stack(0x05a60000,0x05ab0000)]
0x04eb8400 JavaThread “CacheCleanUpThread” daemon [_thread_blocked, id=3420, stack(0x059d0000,0x05a20000)]
0x04eb8000 JavaThread “CacheMemoryCleanUpThread” daemon [_thread_blocked, id=2396, stack(0x05940000,0x05990000)]
0x04eb7400 JavaThread “SysExecutionTheadCreator” daemon [_thread_blocked, id=4620, stack(0x05100000,0x05150000)]
0x01e4a000 JavaThread “Java Plug-In Heartbeat Thread” [_thread_blocked, id=3300, stack(0x05720000,0x05770000)]
0x04eb3c00 JavaThread “AWT-EventQueue-0″ [_thread_blocked, id=1644, stack(0x05690000,0x056e0000)]
=>0x04eb0c00 JavaThread “AWT-Windows” daemon [_thread_in_native, id=4720, stack(0x05570000,0x055c0000)]
0x04ea9c00 JavaThread “AWT-Shutdown” [_thread_blocked, id=1896, stack(0x05480000,0x054d0000)]
0x04ea9400 JavaThread “Java2D Disposer” daemon [_thread_blocked, id=1848, stack(0x052e0000,0x05330000)]
0x01e4c000 JavaThread “Java Plug-In Pipe Worker Thread (Client-Side)” daemon [_thread_in_native, id=3596, stack(0x05190000,0x051e0000)]
0x04ea0c00 JavaThread “Timer-0″ [_thread_blocked, id=3592, stack(0x05070000,0x050c0000)]
0x01e23800 JavaThread “traceMsgQueueThread” daemon [_thread_blocked, id=3144, stack(0x04b90000,0x04be0000)]
0x01e12400 JavaThread “Low Memory Detector” daemon [_thread_blocked, id=364, stack(0x04a70000,0x04ac0000)]
0x01dfbc00 JavaThread “C1 CompilerThread0″ daemon [_thread_blocked, id=2848, stack(0x049e0000,0x04a30000)]
0x01df8800 JavaThread “Attach Listener” daemon [_thread_blocked, id=1524, stack(0x04950000,0x049a0000)]
0x01df5800 JavaThread “Signal Dispatcher” daemon [_thread_blocked, id=3604, stack(0x048c0000,0x04910000)]
0x01df2800 JavaThread “Finalizer” daemon [_thread_blocked, id=4604, stack(0x04830000,0x04880000)]
0x01ded400 JavaThread “Reference Handler” daemon [_thread_blocked, id=4528, stack(0x047a0000,0x047f0000)]
0x002da800 JavaThread “main” [_thread_in_native, id=3228, stack(0x00470000,0x004c0000)]
Other Threads:
0x01db1800 VMThread [stack: 0x02030000,0x02080000] [id=4552]
0x01e13000 WatcherThread [stack: 0x04b00000,0x04b50000] [id=2392]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 5056K, used 1950K [0×24640000, 0x24bb0000, 0x29b90000)
eden space 4544K, 38% used [0×24640000, 0x247f88a8, 0x24ab0000)
from space 512K, 36% used [0x24ab0000, 0x24adf2a8, 0x24b30000)
to space 512K, 0% used [0x24b30000, 0x24b30000, 0x24bb0000)
tenured generation total 10944K, used 6027K [0x29b90000, 0x2a640000, 0×34640000)
the space 10944K, 55% used [0x29b90000, 0x2a172fc8, 0x2a173000, 0x2a640000)
compacting perm gen total 12288K, used 5764K [0×34640000, 0×35240000, 0×38640000)
the space 12288K, 46% used [0×34640000, 0x34be1028, 0x34be1200, 0×35240000)
ro space 10240K, 51% used [0×38640000, 0x38b6dff8, 0x38b6e000, 0×39040000)
rw space 12288K, 55% used [0×39040000, 0x396dc208, 0x396dc400, 0x39c40000)
Code Cache [0x027a0000, 0x029b0000, 0x047a0000)
total_blobs=1129 nmethods=902 adapters=162 free_code_cache=31412352 largest_free_block=256
Dynamic libraries:
0×00400000 – 0×00424000 C:\Program Files (x86)\Java\jre6\bin\java.exe
0×77440000 – 0x775c0000 C:\Windows\SysWOW64\ntdll.dll
0×75480000 – 0×75590000 C:\Windows\syswow64\kernel32.dll
0×75910000 – 0×75956000 C:\Windows\syswow64\KERNELBASE.dll
0x75e90000 – 0x75f30000 C:\Windows\syswow64\ADVAPI32.dll
0×75140000 – 0x751ec000 C:\Windows\syswow64\msvcrt.dll
0x758e0000 – 0x758f9000 C:\Windows\SysWOW64\sechost.dll
0x75a90000 – 0x75b80000 C:\Windows\syswow64\RPCRT4.dll
0x74b30000 – 0x74b90000 C:\Windows\syswow64\SspiCli.dll
0x74b20000 – 0x74b2c000 C:\Windows\syswow64\CRYPTBASE.dll
0x72a00000 – 0x72a4c000 C:\Windows\system32\apphelp.dll
0x720a0000 – 0x7212d000 C:\Windows\AppPatch\AcLayers.DLL
0x74cc0000 – 0x74dc0000 C:\Windows\syswow64\USER32.dll
0x750b0000 – 0×75140000 C:\Windows\syswow64\GDI32.dll
0×77410000 – 0x7741a000 C:\Windows\syswow64\LPK.dll
0x74f80000 – 0x7501d000 C:\Windows\syswow64\USP10.dll
0x75f30000 – 0x76b7a000 C:\Windows\syswow64\SHELL32.dll
0x74b90000 – 0x74be7000 C:\Windows\syswow64\SHLWAPI.dll
0×75780000 – 0x758dc000 C:\Windows\syswow64\ole32.dll
0×75020000 – 0x750af000 C:\Windows\syswow64\OLEAUT32.dll
0×72770000 – 0×72787000 C:\Windows\system32\USERENV.dll
0x732e0000 – 0x732eb000 C:\Windows\system32\profapi.dll
0x72f50000 – 0x72fa1000 C:\Windows\system32\WINSPOOL.DRV
0×72750000 – 0×72762000 C:\Windows\system32\MPR.dll
0x75a30000 – 0x75a90000 C:\Windows\system32\IMM32.DLL
0×75960000 – 0x75a2c000 C:\Windows\syswow64\MSCTF.dll
0x7c340000 – 0x7c396000 C:\Program Files (x86)\Java\jre6\bin\msvcr71.dll
0x6d7f0000 – 0x6da9f000 C:\Program Files (x86)\Java\jre6\bin\client\jvm.dll
0x72bc0000 – 0x72bf2000 C:\Windows\system32\WINMM.dll
0x6d7a0000 – 0x6d7ac000 C:\Program Files (x86)\Java\jre6\bin\verify.dll
0x6d320000 – 0x6d33f000 C:\Program Files (x86)\Java\jre6\bin\java.dll
0x752a0000 – 0x752a5000 C:\Windows\system32\PSAPI.DLL
0x6d7e0000 – 0x6d7ef000 C:\Program Files (x86)\Java\jre6\bin\zip.dll
0x6d420000 – 0x6d426000 C:\Program Files (x86)\Java\jre6\bin\jp2native.dll
0x6d1d0000 – 0x6d1e3000 C:\Program Files (x86)\Java\jre6\bin\deploy.dll
0×75630000 – 0x7574d000 C:\Windows\syswow64\CRYPT32.dll
0×75590000 – 0x7559c000 C:\Windows\syswow64\MSASN1.dll
0x75c00000 – 0x75d1a000 C:\Windows\syswow64\WININET.dll
0×75900000 – 0×75903000 C:\Windows\syswow64\Normaliz.dll
0x74dc0000 – 0x74f76000 C:\Windows\syswow64\iertutil.dll
0x75d20000 – 0x75e30000 C:\Windows\syswow64\urlmon.dll
0x6d6a0000 – 0x6d6e6000 C:\Program Files (x86)\Java\jre6\bin\regutils.dll
0x732f0000 – 0x732f9000 C:\Windows\system32\VERSION.dll
0x6d600000 – 0x6d613000 C:\Program Files (x86)\Java\jre6\bin\net.dll
0x74bf0000 – 0x74c25000 C:\Windows\syswow64\WS2_32.dll
0x75e30000 – 0x75e36000 C:\Windows\syswow64\NSI.dll
0×72690000 – 0x726cc000 C:\Windows\system32\mswsock.dll
0x73e20000 – 0x73e26000 C:\Windows\System32\wship6.dll
0x6d620000 – 0x6d629000 C:\Program Files (x86)\Java\jre6\bin\nio.dll
0x6d000000 – 0x6d14b000 C:\Program Files (x86)\Java\jre6\bin\awt.dll
0x72fb0000 – 0x7314e000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
0x72b10000 – 0x72b94000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll
0x72c00000 – 0x72c13000 C:\Windows\system32\DWMAPI.DLL
0x731f0000 – 0×73270000 C:\Windows\system32\uxtheme.dll
0x72c20000 – 0x72c28000 C:\Windows\system32\Secur32.dll
0x6d230000 – 0x6d27f000 C:\Program Files (x86)\Java\jre6\bin\fontmanager.dll
0×72700000 – 0×72744000 C:\Windows\system32\dnsapi.DLL
0x726e0000 – 0x726fc000 C:\Windows\system32\iphlpapi.DLL
0x72bb0000 – 0x72bb7000 C:\Windows\system32\WINNSI.DLL
0x6d780000 – 0x6d788000 C:\Program Files (x86)\Java\jre6\bin\sunmscapi.dll
0x72f30000 – 0x72f46000 C:\Windows\system32\CRYPTSP.dll
0x72ef0000 – 0x72f2b000 C:\Windows\system32\rsaenh.dll
0x6d1a0000 – 0x6d1c3000 C:\Program Files (x86)\Java\jre6\bin\dcpr.dll
0x73fc0000 – 0x73fd0000 C:\Windows\system32\NLAapi.dll
0x73e10000 – 0x73e20000 C:\Windows\system32\napinsp.dll
0x6eb90000 – 0x6eba2000 C:\Windows\system32\pnrpnsp.dll
0×73550000 – 0×73577000 C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
0x6eb80000 – 0x6eb88000 C:\Windows\System32\winrnr.dll
0×73580000 – 0×73585000 C:\Windows\System32\wshtcpip.dll
0×72630000 – 0×72636000 C:\Windows\system32\rasadhlp.dll
0×73510000 – 0×73548000 C:\Windows\System32\fwpuclnt.dll
VM Arguments:
jvm_args: -D__jvm_launched=1508123368 -Xbootclasspath/a:C:\\PROGRA~2\\Java\\jre6\\lib\\deploy.jar;C:\\PROGRA~2\\Java\\jre6\\lib\\javaws.jar;C:\\PROGRA~2\\Java\\jre6\\lib\\plugin.jar -Dsun.awt.warmup=true -Dsun.plugin2.jvm.args=-D__jvm_launched=1508123368 “-Xbootclasspath/a:C:\\\\PROGRA~2\\\\Java\\\\jre6\\\\lib\\\\deploy.jar;C:\\\\PROGRA~2\\\\Java\\\\jre6\\\\lib\\\\javaws.jar;C:\\\\PROGRA~2\\\\Java\\\\jre6\\\\lib\\\\plugin.jar” “-Djava.class.path=C:\\\\PROGRA~2\\\\Java\\\\jre6\\\\classes” -Dsun.awt.warmup=true — —
java_command: sun.plugin2.main.client.PluginMain write_pipe_name=jpi2_pid2728_pipe3,read_pipe_name=jpi2_pid2728_pipe2
Launcher Type: SUN_STANDARD
Environment Variables:
PATH=C:\Program Files (x86)\Internet Explorer;;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Calibre2\
USERNAME=joseph popolow
OS=Windows_NT
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
————— S Y S T E M —————
OS: Windows 7 Build 7601 Service Pack 1
CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 23 stepping 10, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1
Memory: 4k page, physical 4094900k(2494700k free), swap 8187952k(6427404k free)
vm_info: Java HotSpot(TM) Client VM (20.1-b02) for windows-x86 JRE (1.6.0_26-b03), built on May 4 2011 00:50:59 by “java_re” with MS VC++ 7.1 (VS2003)
time: Tue Jun 21 14:31:31 2011
elapsed time: 377 seconds
Thank you,
Joseph H Popolow
June 23, 2011 at 3:21 pm
Joseph, not sure I can help out here (this is a topic for Windows Update problems, hehe). I’d try uninstalling Java and reinstalling the latest bits from http://www.java.com, tough.
Best, Sandro
September 26, 2012 at 9:20 pm
I was having this same problem with Windows Update Services… Real PITA for me… For sure… I tried everything you can think of, still no success. I asked Microsoft but you know them… NO HELP!!!… I tried all of Microsoft’s fixes, Hot or Not…Crap… Especially with Windows 7 Service pack 1…Every other update would install but when it came to the Service Pack, I tell you no success. It would take forever and when it finally made it’s mind up it would throw errors, different ones each time.I begin one morning to initiate a process of emlinination scheme and found something interesting… To say the least.
I found the problem to exist with the current .DotNET Framework installations. the Service Pack must contain a .Dot NET Framework update. This particular update is somehow conflicting with the current .DotNET Framework install(s).
I know this may seem dumb but I found that if I uninstalled all the current .DotNET Framework installation(s), then proceeded with the service pack Haha!!!… It worked…
September 26, 2012 at 9:30 pm
If you cannot wait then use this link to download the Sercive Pack and manually install it yourself.
http://www.microsoft.com/en-us/download/details.aspx?id=5842