Replies

“Another fix prevents PowerShell from eating a PC alive by creating an infinite number of child directories. “This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding,” Microsoft explained.”

Microsoft actually released an OS that does this. What incompetence. Did they even test it? They must have hired some left over Range Rover engineers.

Microsoft actually released an OS that does this. What incompetence. Did they even test it?

Microsoft has historically made such blunders. There are fewer types of doohickeys to support now, and more uniform standards, so it should get easier, not harder.

My favorite Microsoft blunder was with the original Windows 95. It was their first environment that would adjust to Daylight Savings Time automatically. If you left your computer on overnight, the system would check to see if 2:00 AM hit, and then set the clock back an hour. BUT IT DIDN'T SET A FLAG! So, an hour later, when the clock hit 2 AM again, the clock got set back another hour, etc.

> Microsoft actually released an OS that does this. What incompetence. Did they even test it? They must have hired some left over Range Rover engineers.

What puzzles me is that this bug did not exist prior to this release. What the hell? Does PowerShell not test for the validity of a folder move prior to doing it? Does it not check the destination first?

The Move is trivial mistake to make -- moving a folder into a folder that's actually a subfolder of the original. I imagine that hundreds of computers users do that every day. So I can't believe this bug pre-existed. That kind of programming error is egregious enough, but the lack of testing is worse.

And yet it's announced without even a hint of embarrassment. "Oh, yeah, we let you do a command that scribbles all over your disk until it's full, and then locks up and crashes the operating system, so that you have to figure out why it won't boot properly, and how to fix it."

It's really rather horrifying, when you consider what else didn't get properly vetted and tested, that will be quietly announced next week.