Comments on: Superfail update http://DjLizard.net/2006/08/14/175/ Aw dawg, this is just my whateva-whateva site. Wed, 05 Oct 2011 15:12:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tekgirl http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-6308 Tekgirl Wed, 07 Jul 2010 16:52:45 +0000 http://DjLizard.net/2006/08/14/175#comment-6308 I have tried using dial-a-fix before with no luck (on a particular win2k machine that has been dying a slow death)... took another look at it today, tried your updated steps w/ the .reg file - and voila!!! It is WORKING AGAIN!!! Awesome - many thanks. I have tried using dial-a-fix before with no luck (on a particular win2k machine that has been dying a slow death)… took another look at it today, tried your updated steps w/ the .reg file – and voila!!! It is WORKING AGAIN!!! Awesome – many thanks.

]]> By: gary http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-6275 gary Mon, 07 Jun 2010 11:06:39 +0000 http://DjLizard.net/2006/08/14/175#comment-6275 Brilliant, I had all manner of services that wouldn't start, no icons in network connections, no windows update and this appears to have resolved? Thanks Brilliant, I had all manner of services that wouldn't start, no icons in network connections, no windows update and this appears to have resolved?

Thanks

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-5355 DjLizard Wed, 21 Oct 2009 23:41:34 +0000 http://DjLizard.net/2006/08/14/175#comment-5355 Windows 7 is so good it's <i>retarded</i>. Windows 7 is so good it's retarded.

]]> By: Gary2 http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-5354 Gary2 Wed, 21 Oct 2009 18:08:39 +0000 http://DjLizard.net/2006/08/14/175#comment-5354 Hi, Well, yes, Win2ZK is near the end, but according to Microsoft extended support runs to July 13, 2010. The also say extended support includes "Security update support" which one would assume means the ability to install critical updates. Since this bug causes BITS to stop functioning... Anyway, I was caught by this bug a couple weeks ago and only now found this fix, meanwhile my networking was messed up. So, I vote for Dial-A-Fix to repair the messed up registry after it's messed up, since MS seems to not be inclined to fix their bugs, even though it's not 2010 yet. Actually me thinks they want to force people not to use Win2K any more. Me, I paid over $2,000 for my Win2K as part of MSDN universal and it's a solid OS now. I really don't want to upgrade. (And from what I've heard Vista is not an upgrade, we'll see about Win7.) Gary Hi,

Well, yes, Win2ZK is near the end, but according to Microsoft extended support runs to July 13, 2010. The also say extended support includes "Security update support" which one would assume means the ability to install critical updates.

Since this bug causes BITS to stop functioning…

Anyway, I was caught by this bug a couple weeks ago and only now found this fix, meanwhile my networking was messed up.

So, I vote for Dial-A-Fix to repair the messed up registry after it's messed up, since MS seems to not be inclined to fix their bugs, even though it's not 2010 yet.

Actually me thinks they want to force people not to use Win2K any more.

Me, I paid over $2,000 for my Win2K as part of MSDN universal and it's a solid OS now. I really don't want to upgrade. (And from what I've heard Vista is not an upgrade, we'll see about Win7.)

Gary

]]> By: linda arnold http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-4992 linda arnold Fri, 28 Nov 2008 00:07:02 +0000 http://DjLizard.net/2006/08/14/175#comment-4992 is there a fix for the same problem for xp pro sp2. microsoft was "attached" to my machine to no avail. each time i reboot, i have to restart the services manually to get on the net. id error 4609 among others. is there a fix for the same problem for xp pro sp2. microsoft was "attached" to my machine to no avail. each time i reboot, i have to restart the services manually to get on the net. id error 4609 among others.

]]> By: Jason http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-4933 Jason Tue, 04 Nov 2008 16:49:05 +0000 http://DjLizard.net/2006/08/14/175#comment-4933 One word... Wow! One word… Wow!

]]> By: Gary http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-4742 Gary Thu, 09 Oct 2008 15:55:01 +0000 http://DjLizard.net/2006/08/14/175#comment-4742 I can tell you that this saved me days, if not weeks, of troubleshooting. Thank you very much Gary I can tell you that this saved me days, if not weeks, of troubleshooting.

Thank you very much

Gary

]]> By: Dennis http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-4664 Dennis Thu, 24 Jul 2008 13:53:26 +0000 http://DjLizard.net/2006/08/14/175#comment-4664 What genius!!! I worked on this for days -- tracking one element to another. And Like all the others poured over the MS Knowledge-base and Google searches. And then I found your answer -- such genius! Now if I could just figure out why the DCOM service was also obliterated for my registry, I'd even be more happy. I don't have another 2000 installation from which to copy the relevant keys -- tried using XP's, so far without success. I shall plod on. Thanks heaps! What genius!!! I worked on this for days — tracking one element to another. And Like all the others poured over the MS Knowledge-base and Google searches. And then I found your answer — such genius! Now if I could just figure out why the DCOM service was also obliterated for my registry, I'd even be more happy. I don't have another 2000 installation from which to copy the relevant keys — tried using XP's, so far without success. I shall plod on. Thanks heaps!

]]> By: c http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-4316 c Mon, 03 Mar 2008 03:20:29 +0000 http://DjLizard.net/2006/08/14/175#comment-4316 It won't get fixed, as W2K is way past bug-fix and into extended support. And the problem isn't the .dll itself, it's in setupapi, and that wasn't actually changed until XP. I wouldn't suggest doing this on a 2K box unless you already have the .reg file ready to merge. It won't get fixed, as W2K is way past bug-fix and into extended support. And the problem isn't the .dll itself, it's in setupapi, and that wasn't actually changed until XP. I wouldn't suggest doing this on a 2K box unless you already have the .reg file ready to merge.

]]> By: Nate Coffey http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3998 Nate Coffey Mon, 12 Nov 2007 18:26:59 +0000 http://DjLizard.net/2006/08/14/175#comment-3998 So with all that said..... you done yet? ;) So with all that said….. you done yet?

;)

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3975 DjLizard Fri, 09 Nov 2007 00:49:27 +0000 http://DjLizard.net/2006/08/14/175#comment-3975 Oh yeah, and the reason I <em>do</em> recommend to run #3 (like the blog post says) is that most people who download Dial-a-fix are doing so to fix a Windows Update issue. The other things that #3 does are necessary to fix Windows Update, even though wuaueng will inevitably break your netsvcs key as mentioned further above. Run #3 anyway since you need Windows Update to work, and then fix what wuaueng does by merging the .reg and restarting. Oh yeah, and the reason I do recommend to run #3 (like the blog post says) is that most people who download Dial-a-fix are doing so to fix a Windows Update issue. The other things that #3 does are necessary to fix Windows Update, even though wuaueng will inevitably break your netsvcs key as mentioned further above. Run #3 anyway since you need Windows Update to work, and then fix what wuaueng does by merging the .reg and restarting.

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3974 DjLizard Fri, 09 Nov 2007 00:47:17 +0000 http://DjLizard.net/2006/08/14/175#comment-3974 Nate's right about the API stuff. Dial-a-fix fixes your system by telling your system to fix itself. For example, when you choose "Reinstall <some service>" from the tools menu, it calls rundll32 and hooks into setupapi.dll with an INF from your own system as its main argument (as you can see from its help pane). I had already filed this as a bug with Microsoft, but the unofficial response (from a Microsoft employee not on the WU team) is that it won't be fixed because it's Windows 2000 which was end-of-lifed. I believe this to be untrue however because Windows Update for Windows 2000 has not been end-of-lifed and Windows Update is the one that pushes the buggy DLL. Well, even if it is true that they won't fix it, I believe that they have an obligation to. I'm eagerly awaiting a response from an engineer on the Windows Update team. Also, I did plan on having Dial-a-fix try to detect and avoid this (and insert the missing netsvcs key if necessary) but I haven't had a whole lot of free time to work on Dial-a-fix. I did exactly this, however, with that MSXML bug a while back. It warns you if it notices the buggy version of the DLL. Before anyone else trolls, be sure to remember that Dial-a-fix is <strong>free</strong> and I work on it in my spare time. (If you don't like it, don't use it.) My life priorities list doesn't have Dial-a-fix very high on it. Doing my best and having a roof over my family's head and food on the table comes first. Recently I have nailed several bugs (that <em>are</em> mine) in Dial-a-fix and plan to release a point-release of DAF as soon as I get some of the more egregious stuff fixed. Dial-a-fix can be 1000% smarter than it is and I'm always thinking of ways to improve it. Whether I actually get the time I desire to improve on it is not really up to me. :( Nate's right about the API stuff. Dial-a-fix fixes your system by telling your system to fix itself. For example, when you choose "Reinstall " from the tools menu, it calls rundll32 and hooks into setupapi.dll with an INF from your own system as its main argument (as you can see from its help pane).

I had already filed this as a bug with Microsoft, but the unofficial response (from a Microsoft employee not on the WU team) is that it won't be fixed because it's Windows 2000 which was end-of-lifed. I believe this to be untrue however because Windows Update for Windows 2000 has not been end-of-lifed and Windows Update is the one that pushes the buggy DLL. Well, even if it is true that they won't fix it, I believe that they have an obligation to.

I'm eagerly awaiting a response from an engineer on the Windows Update team.

Also, I did plan on having Dial-a-fix try to detect and avoid this (and insert the missing netsvcs key if necessary) but I haven't had a whole lot of free time to work on Dial-a-fix. I did exactly this, however, with that MSXML bug a while back. It warns you if it notices the buggy version of the DLL.

Before anyone else trolls, be sure to remember that Dial-a-fix is free and I work on it in my spare time. (If you don't like it, don't use it.) My life priorities list doesn't have Dial-a-fix very high on it. Doing my best and having a roof over my family's head and food on the table comes first.

Recently I have nailed several bugs (that are mine) in Dial-a-fix and plan to release a point-release of DAF as soon as I get some of the more egregious stuff fixed.

Dial-a-fix can be 1000% smarter than it is and I'm always thinking of ways to improve it. Whether I actually get the time I desire to improve on it is not really up to me. :(

]]> By: Nate Coffey http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3973 Nate Coffey Thu, 08 Nov 2007 23:20:12 +0000 http://DjLizard.net/2006/08/14/175#comment-3973 The workaround is exactly what he posted in the steps above. He's correct, he has no way of changing how the DllRegisterServer works, and until Microsoft updates it (IF they update it, then I would strongly suggest you just never run #3 on a Windows 2000 computer. He could automate the steps above in the program, but (I'm sure DjLizard agrees with this statement) that is defeating the purpose of this program. The whole idea is to have this program initiate built-in Windows API. The only thing that maybe could be done is to do a check for if the OS is 2000 and disable #3 by default and give a prompt asking if the user is sure they want to go ahead and provide a link to here so they know what they are getting themselves into should they ignore the warning. The workaround is exactly what he posted in the steps above. He's correct, he has no way of changing how the DllRegisterServer works, and until Microsoft updates it (IF they update it, then I would strongly suggest you just never run #3 on a Windows 2000 computer. He could automate the steps above in the program, but (I'm sure DjLizard agrees with this statement) that is defeating the purpose of this program. The whole idea is to have this program initiate built-in Windows API. The only thing that maybe could be done is to do a check for if the OS is 2000 and disable #3 by default and give a prompt asking if the user is sure they want to go ahead and provide a link to here so they know what they are getting themselves into should they ignore the warning.

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3972 DjLizard Thu, 08 Nov 2007 20:22:16 +0000 http://DjLizard.net/2006/08/14/175#comment-3972 What's with the flippant attitude? Do I owe you something? Yeah, I didn't think so. . . Microsoft controls wuaueng's Dll* functions, not me. What's with the flippant attitude? Do I owe you something? Yeah, I didn't think so. . .

Microsoft controls wuaueng's Dll* functions, not me.

]]> By: Aaron Wedemeyer http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3971 Aaron Wedemeyer Thu, 08 Nov 2007 18:07:43 +0000 http://DjLizard.net/2006/08/14/175#comment-3971 So, any ideas how we might get around wuaueng.dll? Yeah, I didn't think so. . . So, any ideas how we might get around wuaueng.dll?

Yeah, I didn't think so. . .

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3910 DjLizard Sat, 20 Oct 2007 17:29:17 +0000 http://DjLizard.net/2006/08/14/175#comment-3910 Aha! I tested Dial-a-fix on a fresh 2000 box and refreshed that area in regedit and it was fine. Then I went to Windows Update and clicked the button to let Windows Update give me a new version of the WU control... and then I immediately ran Dial-a-fix and when I refreshed regedit, netsvcs was gone. I now have the update which causes this problem! <strong>It's wuaueng.dll and its DllInstallServer function is broken.</strong> Aha! I tested Dial-a-fix on a fresh 2000 box and refreshed that area in regedit and it was fine. Then I went to Windows Update and clicked the button to let Windows Update give me a new version of the WU control… and then I immediately ran Dial-a-fix and when I refreshed regedit, netsvcs was gone. I now have the update which causes this problem!

It's wuaueng.dll and its DllInstallServer function is broken.

]]> By: DjLizard http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3909 DjLizard Sat, 20 Oct 2007 17:27:12 +0000 http://DjLizard.net/2006/08/14/175#comment-3909 The bug is in the DLLs themselves - Dial-a-fix calls their DllUnregisterServer and DllRegisterServer functions. This is exactly like the MSHTML bug in that the newer versions of the DLL don't register themselves correctly. I'll file this as a bug with Microsoft ASAP as soon I collect some info and test a bit in my virtual machine. The bug is in the DLLs themselves – Dial-a-fix calls their DllUnregisterServer and DllRegisterServer functions. This is exactly like the MSHTML bug in that the newer versions of the DLL don't register themselves correctly. I'll file this as a bug with Microsoft ASAP as soon I collect some info and test a bit in my virtual machine.

]]> By: Nate Coffey http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3908 Nate Coffey Fri, 19 Oct 2007 16:32:49 +0000 http://DjLizard.net/2006/08/14/175#comment-3908 Ok, I found the specific checkmarks that are breaking. For the WU/WUAU sections, checking "Register WUAU DLLs" deletes the netsvcs value (is that to be expected or maybe that is the bug). It never recreates netsvcs when it reregisters the WUAU DLLs. So when you run Registration center's "Explorer/IE/OE/shell/WMP" it only creates netsvcs with EventSystem and nothing else for the WUAU services. Ok, I found the specific checkmarks that are breaking. For the WU/WUAU sections, checking "Register WUAU DLLs" deletes the netsvcs value (is that to be expected or maybe that is the bug). It never recreates netsvcs when it reregisters the WUAU DLLs. So when you run Registration center's "Explorer/IE/OE/shell/WMP" it only creates netsvcs with EventSystem and nothing else for the WUAU services.

]]> By: Nate Coffey http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3907 Nate Coffey Fri, 19 Oct 2007 16:05:20 +0000 http://DjLizard.net/2006/08/14/175#comment-3907 Oh, another thing too... the only registry value that is incorrect is netsvcs. Here's an export of this value: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost] "netsvcs"=hex(7):45,00,76,00,65,00,6e,00,74,00,53,00,79,00,73,00,74,00,65,00,\ 6d,00,00,00,00,00 And so you don't have to pop that into the registry to read it, that's EventSystem ONLY. Let me get back to you on the exact checkmark that breaks it. Oh, another thing too… the only registry value that is incorrect is netsvcs. Here's an export of this value:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost]
"netsvcs"=hex(7):45,00,76,00,65,00,6e,00,74,00,53,00,79,00,73,00,74,00,65,00,\
6d,00,00,00,00,00

And so you don't have to pop that into the registry to read it, that's EventSystem ONLY. Let me get back to you on the exact checkmark that breaks it.

]]> By: Nate Coffey http://DjLizard.net/2006/08/14/175/comment-page-1/#comment-3906 Nate Coffey Fri, 19 Oct 2007 16:00:23 +0000 http://DjLizard.net/2006/08/14/175#comment-3906 Give me a little bit and I'm sure I can find out. Give me a little bit and I'm sure I can find out.

]]>