[grrr]

[Lifted]

ooh

 

[CZroe]

I've let that little box in the lower right corner sit there for a day or two asking me if I want to reboot or wait.
That's what I told it to do when I installed windows.

Your point? That's precisely what the OP DIDN'T want. He did not want to delay updates just because *some* updates may require a restart.

 

[CZroe]

Yes he said that. He also said that he knew more about this than anyone here. He also said he was an elitist prick basically.

So do you see why he's getting flack now?

It does not make an indefensible position defensible. Microsoft did something wrong. STOP DEFENDING THEM JUST TO POSTURE AGAINST SOMEONE YOU FEEL IS OVER-STATING THEIR ABILITIES!

 

[CVSiN]

"I'm an IT expert" not found.

Next?

learn to read then..
blind following the blind in this case..

and btw people like you condoning stupid people is why I hate ATOT..
right back at you..

 

[Lifted]

It does not make an indefensible position defensible. Microsoft did something wrong. STOP DEFENDING THEM JUST TO POSTURE AGAINST SOMEONE YOU FEEL IS OVER-STATING THEIR ABILITIES!

Sure paints a picture of an insecure person doesn't it?

 

[Lifted]

learn to read then..
blind following the blind in this case..

and btw people like you condoning stupid people is why I hate ATOT..
right back at you..

More personal attacks.

I'm shocked.

Really, I am.

 

[Ns1]

So the fact that you were able to Google a registry key makes you an IT expert and the OP an idiot?

what makes the OP an idiot is losing all his work.

 

[Ghiddy]

He didn't know he was going to suddenly end up in the hospital. I guess you think your grandma will know ahead of time that she's about to fall down the stairs, break her hip, and end up in intensive care so she can hurry back to the computer and change the setting first (God help her if it happens on the way there!)? There are many LOGICAL problems with an auto-install going hand-in-hand with an auto-restart which is PRECISELY why MS did not force auto restarts with installs at one time. Why they suddenly changed it without changing the selectable options is simple: They are retarded. Don't tell me that any thought went into it. Whoever was in charge of designing that specific aspect of user/OS relations failed and failed HARD, just like the guys who seemed to forget what the startup animations were good for when they peppered Windows Vista with long delays on black screens at installation. *rolls eyes* Some idiot decided to implement Aero without vectors or scaling of older applications so we still have applications that break when you change Windows DPI settings that can't just be quickly toggled. The DPI functions are still functionally not usable for the vast majority of users who may want it, like home theater PC users, so it was wasted effort and a stupid call. Same goes for the invisible control box in Vista/7 with no replacement functionality for it's additional Win95C+ functionality.

Don't care. Unless his accident happened while he was at his computer typing his tasks, he has no excuse for not saving his work. I'm guessing that's not the case, because he claimed in another reply that he remoted in to do some work in between bouts of intermittent consciousness. So it's not like his work was there and a freak accident took him away from the computer before he could save his work.

All the other stuff you said, I've already said several times that I agree MS's approach to auto-restart in Win7/Vista is weak. The point i'm making is yes, it's weak, but the OP knew of it ahead of time, and he still didn't save his shit. His rage at MS is misplaced, because he's blaming them for his own mistake.

Put another way: He knew their flaw, yet he didn't change his behavior to adjust for their flaw, and then turns around and tries to blame his lost work on their flaw anyways?

 

[Lifted]

what makes the OP an idiot is losing all his work.

First sentence of the entire thread:

I've been sick and had to abandon a huge amount of incomplete tasks...

I guess you're right. Becoming ill is pretty idiotic. Thanks for clearing that up for me.

 

[Soundmanred]

Your point? That's precisely what the OP DIDN'T want. He did not want to delay updates just because *some* updates may require a restart.

So he did want the computer to restart by itself?
You guys lost me on this one, I have no idea what's going on.
Some people are getting way too invested in this thread...insanity.

 

[Born2bwire]

PEBKAC.

You should let Microsoft download but not install the updates. Or you schedule the updates to run at a time that will not cause problems, like 1 AM. That's what I do. But then again, I'm smart enough not to leave unfinished tasks open on my computer when I am done working for the day. Who the fuck knows what can happen to the computer when I'm away.

 

[disappoint]

doh

 

[CZroe]

I've let that little box in the lower right corner sit there for a day or two asking me if I want to reboot or wait.
That's what I told it to do when I installed windows.

Your point? That's precisely what the OP DIDN'T want. He did not want to delay updates just because *some* updates may require a restart.

So he did want the computer to restart by itself?
You guys lost me on this one, I have no idea what's going on.
Some people are getting way too invested in this thread...insanity.

No. He simply wanted it to automatically start without needing his intervention and to finish when he restarts. He had nothing against being prompted to restart and everything against being forced to restart or opt out of mandatory automatic installation (which he wants). He wants it to behave as it LOGICALLY should and, more importantly, ONCE DID.

 

[KMFJD]

Op managed to pull in a lot, then Lifted threadjacked this into his own troll

 

[Ns1]

First sentence of the entire thread:



I guess you're right. Becoming ill is pretty idiotic. Thanks for clearing that up for me.

did his fingers break and prevent him front hitting CTRL + S? Fever made him forget how to save? Flu made him pass out in front of his desk?

 

[Lifted]

Op managed to pull in a lot, then Lifted threadjacked this into his own troll

:thumbsup:

 

[Jeff7]

What I hate is when I'm typing something and the window pops up (AGAIN) to ask if I want to restart, and I happen to be typing the key that is linked to the "Restart Now" button. Abruptly, my windows are all vanishing as the computer begins to restart itself.

It should simply install the updates, pop up something saying that it's done so, and that a restart will be required, and be done with it. None of the constant nagging prompts every few hours (or every 15 minutes or so if you're on WinXP) with the easily-(mis)triggered restart-now option.

This bit someone where I work, too. The computer automatically installed updates while he was called away from his PC to deal with other tasks, and it apparently proceeded to show the abort/countdown timer and then do the restart on its own.


Yes, I get it, Windows. The computer needs to be restarted to implement the changes. I'll get to it - later. Deal with it, and stop pesting about it.

 

[Ghiddy]

Sort of, except you think that "knowledgeable" = "does not want." The setting is the closest approximation to what he does want but it has one little problem that COULD happen under rare, but common enough, circumstances which he could only HOPE would not affect him ("what if I'm incapacitated and can't return to delay or prepare for the automatic restart?"). MS must expect EVERY user to weigh this possibility before selecting that option and must expect the majority to want it anyway for them to select it as default. Either that or they don't care about user data or they didn't think it through. Considering that they once DID think it through and suddenly changed at the same time as many other clueless changes, I assume that latter and that they were just oblivious to why things were done a certain way in the first place.

No, I do not think that knowledgable = "does not want". He knew the implications of choosing automatic updates. He knew this meant that his computer would restart. Any logical person who knows this and still chooses this option basically takes responsibility for losing any work that comes as a result of an auto-restart + failure to save work.

The irony is that a beginner user is justified in making the OP's mistake. I have lost work too from this; when i first installed Win7 and did not expect Windows to ever restart without confirming w/ me. But the OP, who claimed to know more than all of us about Windows, has known about this bug now, but still didn't do anything to avoid losing his work.

Also, the OP did in fact claim in one of his replies: "I know more than ALL of you here" (about Windows/IT, or "different versions of windows"). If it's not here now, he must have edited his post. Several people saw it, and that's what they are referring to when they say the OP claims to be an IT expert. I don't know if anyone quoted it, but we aren't pulling it out of our ass.

 

[CZroe]

To those saying that this was MS' response to media scrutiny:
Bullshit. What direct threat does a virus pose? Data loss and theft. What does forcing restarts inevitably cause? Data loss. Not forcing a restart does not cause hundreds of thousands of zombie machines to remain on the Internet because the restart WILL inevitably happen. Forcing users to opt out of automatic updates to avoid it would be responsible for FAR MORE delayed patches than simply waiting for the next restart, especially when you can nag them to do it sooner. Also, there is a middle-ground that they did not try before forcing restarts: HALTING the automatic restart is a program refuses to close while still responding, as happens when the OS telling it to close prompts a "Do you want to save?" dialog. This would have minimized their culpability in causing lost data, though it would have still happened (things left typed in web forms, for example).

Don't care. Unless his accident happened while he was at his computer typing his tasks, he has no excuse for not saving his work. I'm guessing that's not the case, because he claimed in another reply that he remoted in to save some work in between bouts of intermittent consciousness. So it's not like his work was there and a freak accident took him away from the computer before he could save his work.

All the other stuff you said, I've already said several times that I agree MS's approach to auto-restart in Win7/Vista is weak. The point i'm making is yes, it's weak, but the OP knew of it ahead of time, and he still didn't save his shit. His rage at MS is misplaced, because he's blaming them for his own mistake.

Put another way: He knew their flaw, yet he didn't change his behavior to adjust for their flaw, and then turns around and tries to blame his lost work on their flaw anyways?

A FLAW is still a FLAW and he still has the RIGHT to complain about it and blame the one responsible for the FLAW for the FLAW existing. You just can't separate blaming MS for the FLAW from blaming himself for knowing about it and still being stung. Your ridicule is obviously not enough to discourage him from speaking the truth.

As for the freak accident: HE ENDED UP IN THE HOSPITAL, YOU MORON! That was why he had to remote and THAT is why he could not maintain consciousness. Jesus.

PEBKAC.

You should let Microsoft download but not install the updates. Or you schedule the updates to run at a time that will not cause problems, like 1 AM. That's what I do. But then again, I'm smart enough not to leave unfinished tasks open on my computer when I am done working for the day. Who the fuck knows what can happen to the computer when I'm away.

This isn't a "who the fuck knows" event. It's an inexcusable behavioral change from the way automatic updates were once performed without user involvement or notification. Even 1AM causes problems when you are incapacitated in the hospital, as the OP was.

 

[darkxshade]

This is what I can only conclude for the OP:


-You knew this could happen[it was unlikely but you knew for a couple years?]
-You [sorta?] knew a way around it
-It wouldn't be something simple like a selectable option but you're an "IT expert" who I assume is smart enough to at least google a way to hack it
-You didn't act on this
-It happens
-You blame MS[which is somewhat valid] while failing to realize your own mistake. Were you expecting your PC to do something else knowing full well what it's going to do if an automatic update were to occur?

The brakes on my car have always worked... recently it felt shoddy while I was driving it... Should I continue driving the car without getting it checked out? If I didn't and I crash, should I blame the brakes for failing? I could, but I could have prevented the crash, it would have required me to go out of may to make it right when it should have worked in the first place but I didn't... so I crashed. Fucking brakes...


The underlying message here is that, the fault starts with the OP. Sure there's enough blame to go around but ultimately this was preventable for which the OP failed to act upon regardless of whether or not it was his responsibility.

 

[CVSiN]

This is what I can only conclude for the OP:


-You knew this could happen[it was unlikely but you knew for a couple years?]
-You [sorta?] knew a way around it
-It wouldn't be something simple like a selectable option but you're an "IT expert" who I assume is smart enough to at least google a way to hack it
-You didn't act on this
-It happens
-You blame MS[which is somewhat valid] while failing to realize your own mistake. Were you expecting your PC to do something else knowing full well what it's going to do if an automatic update were to occur?

The brakes on my car have always worked... recently it felt shoddy while I was driving it... Should I continue driving the car without getting it checked out? If I didn't and I crash, should I blame the brakes for failing? I could, but I could have prevented the crash, it would have required me to go out of may to make it right when it should have worked in the first place but I didn't... so I crashed. Fucking brakes...


The underlying message here is that, the fault starts with the OP. Sure there's enough blame to go around but ultimately this was preventable for which the OP failed to act upon regardless of whether or not it was his responsibility.

dude that was your 9999 post! nice
1 more for lifer!

 

[CZroe]

did his fingers break and prevent him front hitting CTRL + S? Fever made him forget how to save? Flu made him pass out in front of his desk?

You are being sarcastic, but the answer is: YES. He ended up being suddenly overcome and admitted to the hospital.

 

[CZroe]

What I hate is when I'm typing something and the window pops up (AGAIN) to ask if I want to restart, and I happen to be typing the key that is linked to the "Restart Now" button. Abruptly, my windows are all vanishing as the computer begins to restart itself.

It should simply install the updates, pop up something saying that it's done so, and that a restart will be required, and be done with it. None of the constant nagging prompts every few hours (or every 15 minutes or so if you're on WinXP) with the easily-(mis)triggered restart-now option.

This bit someone where I work, too. The computer automatically installed updates while he was called away from his PC to deal with other tasks, and it apparently proceeded to show the abort/countdown timer and then do the restart on its own.


Yes, I get it, Windows. The computer needs to be restarted to implement the changes. I'll get to it - later. Deal with it, and stop pesting about it.

Yes. Stealing input focus like that is unforgivable. I don't like Apple products, but I use them as an example: An Apple product would NEVER allow this. NEVER. It is inexcusable for MS to CONTINUE to do this despite DECADES of supposed UI "innovation." File copy dialogs after large downloads still steal focus and cancel with a press of the most commonly typed key (space) and delete the temporary files in a way where a browser cannot resume the file download. INEXCUSABLE. If I were a project manager on the Windows team, I would DEAMND to know who is responsible and FIRE THEM (assuming they still work there, considering the amount of time this has gone on). I would not give them the option to fix it and remain because that is a FUNDAMENTAL ERROR that serves to show their flawed logic and priorities will affect everything else that they do. They should not have any further involvement with something as pervasive and relied upon as Windows and are DIRECTLY impacting consumer perception of their primary product and causing an intensely negative user experience for millions over decades.

 

[Numenorean]

So the fact that you were able to Google a registry key makes you an IT expert and the OP an idiot?

No, I think my MCITP and VCP certifications as well as some of the jobs I've done would be enough for me to consider myself an IT expert. I haven't claimed to know everything though, unlike the OP who says he knows more than everyone.

 

[Ghiddy]

A FLAW is still a FLAW and he still has the RIGHT to complain about it and blame the one responsible for the FLAW for the FDLAW existing. You just can't separate blaming MS for the FLAW from blaming himself for knowing about it and still being stung. Your ridicule is obviously not enough to discourage him from speaking the truth.

Yes, I believe most here would acknowledge the flaw. But we all still ridicule the OP for knowing about it and still trying to flame MS for his failure to save his work. That will never change no matter how much you try to convince us otherwise. Yes, you can be really narrow and say MS has a flaw, but that's besides the point. We don't live in a vacuum where you can just cling to that one thing. While that is true, it is a flaw, the OP tried to blame the flaw when his own neglect caused him to lose work.

Another way to look at what you just said:
If there is a salmonella outbreak for Jiffy brand peanut butter all over the news, and you see several news stories about deaths because of it, would you still continue to make sandwiches with Jiffy peanut butter that you you purchased before you heard about the outbreak?

As for the freak accident: HE ENDED UP IN THE HOSPITAL, YOU MORON! That was why he had to remote and THAT is why he could not maintain consciousness. Jesus.

Yes, he ended up in the hospital, I understand that. I've been in the hospital too, and have worked remotely while not being able to get out of bed due to life threatening illness as well. So? You claimed that he was unable to save his work because of some freak accident. I'm saying that has nothing to do with the mistake he made.

Let's assume he had unsaved work when his accident took place. This means he left his computer with unsaved work. That's his bad.

Let's assume the accident happened while he was at his computer. He still remoted into his computer several times, in between intermittent bouts of consciousness, and still failed to save his work. That's still his bad.

Let's assume the saved work is all stuff he started while he was in the hospital, remoting in, and he didn't save it before the auto-restart. That's STILL his bad.