| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
'Stealth' Windows updates may do harm, says newsletter | |
|
||
| Time: 02:34 EST/07:34 GMT | News Source: Seattle PI | Posted By: Kenneth van Surksum | ||
|
Fixes made by Microsoft to installed copies of Windows without the user's knowledge or permission -- detailed here earlier this month -- at first seemed alarming but harmless. A story set to appear Thursday in Windows Secrets newsletter says that's not so. "We have tested and confirmed that the silent updates actually prevent a Nate Clinton, Microsoft's program manager for the Windows Update program, couldn't be reached for comment late Wednesday afternoon. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 313 Last | Next |
The time now is
10:52:14 AM
ET.
Any comment problems? E-mail us |
| #1 By 25406 (124.169.166.156) at 9/27/2007 4:40:13 AM |
|
Umm, I've seen that problem for years now and I just run Dial-A-Fix to get WU working again after a repair reinstall.
I'm more than a little surprised that others haven't encountered it more often! edit: Heck, there is even a KB about it http://support.microsoft.com/kb/555615 about update problems after a repair. It's only a year old ;) This post was edited by marbleless on Thursday, September 27, 2007 at 04:45. |
| #2 By 23275 (71.12.191.230) at 9/27/2007 10:56:56 AM |
|
#1, Excellent Post!
No hysteria - just a challenge identified and a solution shared - no grand conspiracy - no drama - just an engineer offering some help. Very refreshing. You are right, the problem has been around for some time and the associated and linked error codes offered do lead to the fix you offered and others. Too bad the author of the article wasn't as thoughtful as yourself. |
| #3 By 7711 (209.204.74.18) at 9/27/2007 11:16:00 AM |
|
#2...I agree that it is refreshing to see a solution with no sniping or flames.
But I did read the article (I subscribe to that newsletter), and I think their point is that WU should not cause that type of problem due to poorly registered or unregistered dll's. It is MS's own update program, for Pete's sake!! I'm not sure why this issue hasn't been fixed. It's similar to the issue of Windows Desktop Search in XP....install it, but then there's no easy way to uninstall it. It's their own program for their own OS...it shouldn't have that type of issue. |
| #4 By 37047 (216.191.227.68) at 9/27/2007 11:17:57 AM |
|
For those who don't want to read the article, or for those accessing this after the link is dead, here is the crux of the fix. Run these commands from the command line, or put them into a batch file for ease of execution:
regsvr32 /s wuapi.dll regsvr32 /s wuaueng1.dll regsvr32 /s wuaueng.dll regsvr32 /s wucltui.dll regsvr32 /s wups2.dll regsvr32 /s wups.dll regsvr32 /s wuweb.dll These will register the dll files that the updated WU installer didn't. |
| #5 By 37047 (216.191.227.68) at 9/27/2007 11:21:08 AM |
| Rule #1 of software installers: Test on a fresh installation of Windows. In this case, a fresh Original install, a fresh SP1 install, and a fresh SP2 install, and insure that it works with all of them, and probably many steps in between too, like each WU version upgraded to the latest. This should not be a problem for a testing lab as extensive as Microsoft's. |
| #6 By 25406 (124.169.166.156) at 9/27/2007 12:42:27 PM |
|
Fresh installs aren't a problem, it's when repair installs are done over XP systems that have later WU files than the ones on the boot CD.
I've never figured out why WU works after some repairs and not others. Checking and if necessary re-registering WU is now just another part of my repair procedure as I check the rest of the system is working properly (after all it is a 'repair'!). And thanks for the supportive messages. It's nice to know I'm not spending my time talking to a vacuum :) |
| #7 By 2960 (68.100.112.199) at 9/27/2007 2:29:02 PM |
|
I don't allow these, so it should not affect us.
TL |
| #8 By 15406 (216.191.227.68) at 9/27/2007 3:42:02 PM |
|
Regardless of the apologies and workarounds, MS should not ever update a system without disclosing what's it's doing and giving the user a chance to intervene. The average user would not know how to fix this problem, or even where to go for help.
|
| #9 By 8556 (12.210.39.82) at 9/27/2007 4:11:12 PM |
| Mystic: Thanks for sharing. I was going to post the commands, but you beat me to it. I've used the commands you listed to repair Windows Update for a while. They work every time after a repair install. I do restart the PC after running the last command. Then I watch the automatic updates begin working again, or use Windows Update if I want to stare at the screen for a long period of time. |
| #10 By 23275 (172.16.10.31) at 9/27/2007 5:41:18 PM |
|
#8, Not true. WU errors produce codes and links to solutions articles visible to end users on the page.
BTW... these challenges have always been applicable to post repair operations - e.g., as when using the recovery console /R and or /P to repair a Windows install. The OS is restored to a state prior to many updates [depends upon the media used and the time elapsed since it was produced]. Also, end users may well not know what to do - this is why either Microsoft [retail support period, or paid support] and OEM support exist. Yes, we all agree that there should be a notice, but this issue is not the same thing, or context. The same would apply if a person was auto-updating or manually selecting updates and then ran a repair. And TL, you use WSUS, or SUS, but many similar issues - though based upon different code, would also apply. The article may intend to inform, but it fails to do that - it obfustactes a larger truth for hits - the worst reason to write an article. |
| #11 By 2960 (68.100.112.199) at 9/28/2007 9:12:17 AM |
|
Actually, we use Patchlink, but I get your point :)
TL |
|
Write Comment
Return to News |
Displaying 1 through 25 of 313 Last | Next |
The time now is
10:52:14 AM
ET.
Any comment problems? E-mail us |
