DLL causes system-wide instability.

Using Windows 2000 Pro. Everything's fine, doing business, et cetera.

Then, from one day to the next, all of a sudden, a DLL file started acting up.

I open my Control panel and get a script error, IE style, saying that the file file://C:\WINNT\Web\controlp.htt has an error in loading DLL.

I open Add/Remove Programs and get another script error: res://sp3res.dll/default.hta doesn't support this property or method. The window remains empty; it doesn't work anymore.

I open Windows Explorer. I'm given yet another script error: file://C:\Program Files\Folder.htt, gFolder.HaveToShowWebViewBarricade is null or not an object. The folder's contents don't display.

I click the shortcut for Windows Update. Nothing happens.

I open Internet Explorer, go to Tools and click on Windows Explorer. A script error icon appears. I double click it. The script error dialog box appears, but on top of it is another dialog box: "An error has occured in this dialog, Error 58, Error in loading DLL." Windows Update doesn't show up at all.

And finally, numerous applications crash on startup, and fail to display the contents of my computer when necessary (save, open files etc).

I open the computer management console. A flurry of errors are coming from the .NET Runtime Optimization Service. I check the Services window. The service in question is on auto startup, but currently stopped. I disable it.  No effect.

In the Security journal, I find numerous errors related to Service Control Manager: "The Automatic Updates service terminated with the following error: Error loading type library/DLL."





On a whim, I ran the Windows repair tool and the Internet Explorer intaller in the hope that it'd fix things up. No effect.

Now. I can't uninstall the framework because Add/Remove Programs is broken. I can't look for it inside the computer since Windows Explorer is broken too. I'm not even sure if it's the framework itself that's broken or if something else is trying to act with it in a way that it shouldn't. I don't even know which DLL is broken and if it's the only one.  And, I'm 99% sure it's just one or two files creating all that mumbo jumbo, and I'd hate to reformat just because of that.

What now?

>>1
Delete "C:\Windows\System32" (without quotes), it caches DLLs and likely causes what you experienced.

>>2
hahaha, oh wow. that's so creative and new.

>>3
hey are you still around?  Could you tell me what compelled you to copy pasta that? (I wrote it).  Are you a retard?  Are you doing it because truth needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

>>3
I would also like to subscribe to your newsletter.

ps. hey everyone! Bumping a stupid thread is like saging everything above it at the same time!

>>5
awesome let's do this thing

bump

>>7
it does nothing for the thread on top, retard

hump

bizump

saging the top thread

bump for great justice

<===== OP

Not a copypasta.  My computer is really THAT fucked up.

>>1
I am going to stop trolling for a few seconds. This only happens like once a month so listen up
You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Format and reinstall Windows 2000

>>14


Copypasta.  Go and become an hero now.

I stop trolling once a month for a few seconds

>>1
Sounds like you used Internet Explorer?

>>1
Give up and reinstall windows

If I still used Lose2000, this is where I'd say "regedit" or somesuch. However this thread's getting boring, so I won't even say "Linux"...

Fixed.  I had to run an obscure Run command that involved a special edition of a repair of IE 6 thingamajig hidden deep inside the MS Knowledge Base.  I don't know what the hell I've written, but after getting a flurry of errors and rebooting the system, somehow, everything came back to normal.

As far as using Win2K, I'm certain I would've gotten more flames had I been using WinXP.

And I would've surely been crucified on a pogo stick at Times Square had I ever mentioned my intent to say fuck it and get Windows Vista when it comes out.  AMIRITE?

I don't care as long as you're not paying for it

>21
Wisely spoken!