Internet Not Responding

[nicrune007]

 

I hate to say it, but there is probably nothing we can do about your PC then. Looks like you've been [bleep]-ed by the people that made the OS

 

 

 

~Mr. Devnull

 

 

 

What do you mean?

[blade995]

 

I hate to say it, but there is probably nothing we can do about your PC then. Looks like you've been [bleep]-ed by the people that made the OS

 

 

 

~Mr. Devnull

 

 

 

What do you mean?

 

 

 

Don't listen to him, there's always something you can do to fix your computer. He just has a habit of when he has no idea what's wrong, he blames Windows.

[D. V. Devnull]

 

I hate to say it, but there is probably nothing we can do about your PC then. Looks like you've been [bleep]-ed by the people that made the OS

 

What do you mean?

 

Don't listen to him, there's always something you can do to fix your computer. He just has a habit of when he has no idea what's wrong, he blames Windows.

 

Very funny, blade995. :lol: ... You should go check out the talkback threads for a ton of the articles on ZDNet. Once MicroSoft gets you with a bad update package, you start having problems, and they don't go away without a format and total reinstall. There are literally horror stories posted of people who have Windows PCs that, among other things, have changed their internal settings on their own and not listened to the user, auto-updated at Windows Update, and re-booted while someone was playing "World Of Warcraft" or was working on some really important project, and these PCs gave NO NOTICE of what they were about to do. This resulted in crashed PCs and hundreds of hours of work lost.

 

 

 

And then you think I have no good reason to be blaming MicroSoft? Think again, and then think again some more. I've just shown yet another good reason to blame them!

 

 

 

~Mr. Devnull

[Cruiser]

Very funny, blade995. :lol: ... You should go check out the talkback threads for a ton of the articles on ZDNet. Once MicroSoft gets you with a bad update package, you start having problems, and they don't go away without a format and total reinstall. There are literally horror stories posted of people who have Windows PCs that, among other things, have changed their internal settings on their own and not listened to the user, auto-updated at Windows Update, and re-booted while someone was playing "World Of Warcraft" or was working on some really important project, and these PCs gave NO NOTICE of what they were about to do. This resulted in crashed PCs and hundreds of hours of work lost.

 

 

 

And then you think I have no good reason to be blaming MicroSoft? Think again, and then think again some more. I've just shown yet another good reason to blame them!

 

 

 

~Mr. Devnull

 

That is not a windows problem. That is a user stupidity problem. It is NOT Microsoft's fault the user left Automatic Updates on and happened to be playing WoW when the time to update showed up. It is a well known fact that AU downloads, installs, and reboots without notice. Using AU updates on it's own isn't the smartest of things to do for exactly those reasons. That is exactly what it's suppose to do. Stop trying to flame MS software for doing exactly what it is suppose to being doing.

 

 

 

The stuff you cite (by proxy, source it next time) is easily fixed by actually taking a bit of time to review the updates being installed and by doing it yourself. Once again, you've proven you use your opinion sprinkled with a few weak supporting stories to try and make your point, and failed once again.

[nicrune007]

D_V_Devnull, so what do you think is should do then?

[nicrune007]

D_V_Devnull, so what do you think is should do then?

[D. V. Devnull]

Off-topic:

 

Very funny, blade995. :lol: ... You should go check out the talkback threads for a ton of the articles on ZDNet. Once MicroSoft gets you with a bad update package, you start having problems, and they don't go away without a format and total reinstall. There are literally horror stories posted of people who have Windows PCs that, among other things, have changed their internal settings on their own and not listened to the user, auto-updated at Windows Update, and re-booted while someone was playing "World Of Warcraft" or was working on some really important project, and these PCs gave NO NOTICE of what they were about to do. This resulted in crashed PCs and hundreds of hours of work lost.

 

 

 

And then you think I have no good reason to be blaming MicroSoft? Think again, and then think again some more. I've just shown yet another good reason to blame them!

 

 

 

~Mr. Devnull

 

That is not a windows problem. That is a user stupidity problem. It is NOT Microsoft's fault the user left Automatic Updates on and happened to be playing WoW when the time to update showed up. It is a well known fact that AU downloads, installs, and reboots without notice. Using AU updates on it's own isn't the smartest of things to do for exactly those reasons. That is exactly what it's suppose to do. Stop trying to flame MS software for doing exactly what it is suppose to being doing.

 

 

 

The stuff you cite (by proxy, source it next time) is easily fixed by actually taking a bit of time to review the updates being installed and by doing it yourself. Once again, you've proven you use your opinion sprinkled with a few weak supporting stories to try and make your point, and failed once again.

 

I guess you haven't heard of updates that don't listen to a user's disable on Automatic Updates? And the fact that MicroSoft hides these things and doesn't tell you? And then to finish it off, that in all honesty, there are people at MicroSoft that think a home user is too stupid to handle system updates on their own? Or the fact that in the latest MicroSoft EULAs, MicroSoft stipulates that they can shove software and updates at you as they see fit?

 

 

 

I've also heard that Norton is dependent on MicroSoft's Automatic Updates being enabled, as of their latest versions, and will flip it on in the event that it finds it off. I don't think Nicrune008 is running one of those, so I've ruled it out.

 

 

 

The DOJ needs to take MicroSoft back to court and take them down, once and for all. Otherwise, this [bleep] will never end.

 

 

 

Anywho, let's get back to the topic at hand, and stop with the evil arguing, to which I'm replying below...:

 

 

 

===================================

 

 

 

 

 

ON-TOPIC:

 

D_V_Devnull, so what do you think is should do then?

 

Nicrune008, before I even get close to suggesting a total rebuild, which would mean backing up all the personal data (e-mails/music/documents/downloads/you-name-it) that you have, I just noticed something. I don't remember seeing a "HiJackThis" log in this thread. Now sadly, I'm not one of the best with them, but maybe if you post one, someone who knows how to handle it can come through and tell you anything they know in regard to the info provided by it. Maybe they can see something I haven't possibly thought of.

 

 

 

I'll be back in the near future to check on this thread again. Hopefully we can still nail the problem, but I have to admit, chances of defeating it still seem slim-to-zero to me. :-k

 

 

 

~Mr. Devnull

[blade995]

guess you haven't heard of updates that don't listen to a user's disable on Automatic Updates? And the fact that MicroSoft hides these things and doesn't tell you? And then to finish it off, that in all honesty, there are people at MicroSoft that think a home user is too stupid to handle system updates on their own? Or the fact that in the latest MicroSoft EULAs, MicroSoft stipulates that they can shove software and updates at you as they see fit?

 

 

 

I've also heard that Norton is dependent on MicroSoft's Automatic Updates being enabled, as of their latest versions, and will flip it on in the event that it finds it off. I don't think Nicrune008 is running one of those, so I've ruled it out.

 

 

 

The DOJ needs to take MicroSoft back to court and take them down, once and for all. Otherwise, this [bleep] will never end.

 

 

 

Anywho, let's get back to the topic at hand, and stop with the evil arguing, to which I'm replying below...:

 

 

 

 

Damm, I thought you left for good finally. I guess I can;t always have my way.....

 

 

 

The update that updates itself with having automatic updates off is true but you only got half of the story (what a surprise). Microsoft has stated that this update was for Windows/Microsoft update itself, not for the operating system. Without this update you would not be able to get new updates if you do decide to turn it back on in the future.

 

 

 

I don't know too much about Norton but it's probably not dependent on Norton but enables automatic updates because it protects your computer and is thinking a virus is turning it off. I'm sure there is a setting deep inside the settings to fix this.