I'd managed to get into safe mode with networking, and was trying to get the AMD drivers and DDU. For some reason the entire explorer shell was borked in a very strange manner which caused misbehaviour across a wide variety of builtin apps like cmd, taskmgr, either just not functioning at all, or only partially etc. basic troubleshooting tools just couldn't be used.

For some reason it tried to launch edge as "builtin\administrator" which is essentially equivalent to root. I think I was logged in as a normal user account, so there should have been no elevation.

In the end a complete rollback to the prior OS build version had to be done, and everything sprang back to life - correctly working graphics etc. I think in the end I tried updating several times but the graphics were completely broken. Ended up rolling back again and skipping that update completely - one of my other slashdot comments indicates that it was build 14332.

> The setting is adjustable
No, it DIDN'T.

> and Windows does in fact obey it.
No, it DIDN'T

>You can custom set your own active time (your own timezone), and on top of that specify the exact reboot time.
You can NOW. You couldn't THEN.

Do you want to try and be a little more condescending? possibly with the ability to have some accuracy in what you are talking about?

Or would you like to try some COMPREHENSION first, or is that civility a bit beyond you?

> But then you're trying to run a Microsoft browser with administrator privileges so I don't really peg you for a clever user.

So what would you have done in the situation when safe mode is the only ability you have to get any new drivers? and I want to see the commands and or tools you would have used. And pay attention to what I wasn't able to access.

At the time it was Windows 10 Pro Insider Preview, so the top tier home/home-business version.

In the fast ring that stopped working a few months ago, in just deleting the reboot folder, as in the key is now seemingly non-existent.

The key usually reappeared after a reboot, or the update process had run. I used to leave the computer on (i pretty much have it 24x7) and could extend by a week or two before something caused a crash and required a reboot.

I hadn't seen the creation of a non-SYSTEM reboot folder as being a method to workaround that though.

The only thing I have to say in followup is that Microsoft have made an improvement - Active hours have been extended to 18 hours (ie. I can set it from 11pm to 7am now) and miraculously have learned to actually use this time. Congratulations MS, slow-clap.

And it has now worsened - prior to build 15002 the fast ring would allow you to defer the updates NOTIFIYING YOU that there was one available. Now you wake up in the morning to find, that yes, the computer has rebooted during the night and now you have to find the applications that are fucked. I am particularly looking at you BLUESTACKS. Still not entirely sure how a managed Virtual machine system can get so fucked, but it manages somehow. Only a complete rip out of the program directories and a registry clean will unfuck it enough to reinstall - and you can forget any ability to reuse the prior data. (I'm a bit pissed because Windows 10 fucking updated last night with no notice- and so have to spend an hour or two getting back to where I was before.)

I suppose just being a mere mortal means that as we don't pay for Windows 10 complete with TAMs, account managers, sales reps, we are beneath their notice. It is only going to be a matter of time before this really fucks up for someone prominent. As a fast ring user, it seems that only the shiny feedback is relevant.

Microsoft have gotten entirely too comfortable, and has seemingly let loose the new grads without supervision, and let them yet again regurgitate what has gone before, but with different bugs, and entirely new classes of usability errors due to "touch design".

From an article 10 months ago.

https://tech.slashdot.org/stor...

by marked on 07:47 PM May 4th, 2016 (#52047825) Attached to: Windows 10 Updates Are Now Ruining Pro-Gaming Streams
As a somewhat hardened veteran of software installation, and the unbounded stupidity that arises from boneheaded mistakes that occur, I would like to point out the following:

Windows 10 Update installation does not follow the guidelines for updating as explicitly laid out in your software, that is "we will update when you are not using the computer". To help matters further, we will specifically exclude during the following hours "8am to 5:30pm".

So WHY THE FUCK WAS THERE AN UNCONTROLLED INSTALLATION OF AN OS UPDATE AT 4PM TODAY DURING THE TIME I WAS ACTIVELY USING THE SYSTEM? And when I say uncontrolled, it was not "oh click later to install, it was "we are rebooting now to install, OK". No deferral, no postponement, just instant notice.

Not to mention that the reboot occurred during a very intense multiplayer fight that I was the host of, which effectively drop-kicked several players out into the ether without me being able to contact them to let them know what was going on.

Did you mean 8am - to 5:30pm my local time, or that of the Microsoft HQ, in sunny whereever? It is bad enough that games developers can't actually remember how many days there are in April, yet to fuck up simple time management for updating has to be some fairly serious mismanagement on the part of senior design leads.

Or could it be that it completely ignores it like the boneheaded mechanism that only allows 10hour "active" windows slot, because there is no possible reason why people at home could not be using it from 7 in the morning until midnight? or am I completely in the dark about usability that requires a 14 hour window to update on a daily basis?

Of course to further the boneheaded-ness it completely fucked the graphics drivers, where it greenscreened just at idle on the desktop - to the point I had to continuously reboot until I could get to the stage where I could get a CMD prompt up and manage to type "shutdown /o /r /t 1" to get a relatively swift reboot into a mode where I say yes, I want to run a troubleshooting step, and reboot, and then select safe mode, and then reboot into it.

Not to mention that it has been a known problem with the graphics drivers since the last update, and putting it down to "it is the responsibility of the driver manufacturers (Microsoft Engineer)" is disingenuous at best, as MS is supposed to have WHQL'd the drivers, which means that MS should have caught this problem much earlier in testing during the automated build and test phase.

To top that then off, I can't run Microsoft EDGE because the "built in administrator account can't run it".... I can't run explorer because you've managed to switch of the command searching in the cortana interface, which means that I can't run taskmanager, command, etc. What stupidity of a design decision managed to get authorised to create this situation?

The insider fast ring is supposed to be a way to bring light problems that exist in interaction with components. Fucking with AMD graphics drivers in this way isn't an acceptable manner of implementing software best practices.

Now I have to spend an hour fucking around with Device driver uninstaller, because in the infinite wisdom, you've managed to disable any ability of the driver software to recognise that there is an installed device, so of course the programs bomb out with a "no recognised device" so we won't do anything remotely sensible like uninstall the graphics drivers. Then I have to spend an hour waiting whilst I roll back the installation, then reinstall drivers, then reboot, reset up profiles, and ... then reboot again. That is a considerable amount of unnecessary reboots as you rush to get untested, useless additions out into the population.

Yours,

Entirely Hacked Off

He might be on the Windows 10 fast ring, which updated to 14332. It autoforced installed on me earlier this afternoon for me, to which it has now wasted 4 hours of my time for something that I explicitly told it not to do. See my rant elsewhere in this thread.

Prior to 14328, it was exactly as you described.

As a somewhat hardened veteran of software installation, and the unbounded stupidity that arises from boneheaded mistakes that occur, I would like to point out the following:

Windows 10 Update installation does not follow the guidelines for updating as explicitly laid out in your software, that is "we will update when you are not using the computer". To help matters further, we will specifically exclude during the following hours "8am to 5:30pm".

So WHY THE FUCK WAS THERE AN UNCONTROLLED INSTALLATION OF AN OS UPDATE AT 4PM TODAY DURING THE TIME I WAS ACTIVELY USING THE SYSTEM? And when I say uncontrolled, it was not "oh click later to install, it was "we are rebooting now to install, OK". No deferral, no postponement, just instant notice.

Not to mention that the reboot occurred during a very intense multiplayer fight that I was the host of, which effectively drop-kicked several players out into the ether without me being able to contact them to let them know what was going on.

Did you mean 8am - to 5:30pm my local time, or that of the Microsoft HQ, in sunny whereever? It is bad enough that games developers can't actually remember how many days there are in April, yet to fuck up simple time management for updating has to be some fairly serious mismanagement on the part of senior design leads.

Or could it be that it completely ignores it like the boneheaded mechanism that only allows 10hour "active" windows slot, because there is no possible reason why people at home could not be using it from 7 in the morning until midnight? or am I completely in the dark about usability that requires a 14 hour window to update on a daily basis?

Of course to further the boneheaded-ness it completely fucked the graphics drivers, where it greenscreened just at idle on the desktop - to the point I had to continuously reboot until I could get to the stage where I could get a CMD prompt up and manage to type "shutdown /o /r /t 1" to get a relatively swift reboot into a mode where I say yes, I want to run a troubleshooting step, and reboot, and then select safe mode, and then reboot into it.

Not to mention that it has been a known problem with the graphics drivers since the last update, and putting it down to "it is the responsibility of the driver manufacturers (Microsoft Engineer)" is disingenuous at best, as MS is supposed to have WHQL'd the drivers, which means that MS should have caught this problem much earlier in testing during the automated build and test phase.

To top that then off, I can't run Microsoft EDGE because the "built in administrator account can't run it".... I can't run explorer because you've managed to switch of the command searching in the cortana interface, which means that I can't run taskmanager, command, etc. What stupidity of a design decision managed to get authorised to create this situation?

The insider fast ring is supposed to be a way to bring light problems that exist in interaction with components. Fucking with AMD graphics drivers in this way isn't an acceptable manner of implementing software best practices.

Now I have to spend an hour fucking around with Device driver uninstaller, because in the infinite wisdom, you've managed to disable any ability of the driver software to recognise that there is an installed device, so of course the programs bomb out with a "no recognised device" so we won't do anything remotely sensible like uninstall the graphics drivers. Then I have to spend an hour waiting whilst I roll back the installation, then reinstall drivers, then reboot, reset up profiles, and ... then reboot again. That is a considerable amount of unnecessary reboots as you rush to get untested, useless additions out into the population.

Yours,

Entirely Hacked Off

Of course it does.

It is used to catch the Evil Bits.

Quite possibly.

If it looked anything like an intern had been let loose with an amiga, a genlok, and video toaster - then yes.

If it bad eyesearing visuals that looked somewhat OK on a monitor but then smeared and bled horrifically on what looks like 2nd (if you were lucky) or 3rd gen copy 110 line video with full NTSC effects - then yes.

Yes, because that quite clearly happens with all the laptops, tablets, and mobile phones that have already been up there.

Oh, wait.

You are probably mis-remembering that Michael Weatherly who plays NCIS agent Tony DiNozzo played Logan Cale (Eyes Only) the disabled cyber-activist in James Cameron's Dark Angel.

that would be Steve McConnell. No idea who Mike is.