Normal mode restoring shouldn't depend on user access

[mirh]

In particular, yesterday I lost three hours because I was used to log in Windows with PIN, and safe mode only allows complete password, which of course I forgotten (thankfully I avoided formatting).

Anyway, I indeed see you depends on the program starting again to remove the bcd flag. And I was thinking something that could prevent similar situations should be implemented.

Perhaps relying on a separate bcd "config" for the operation? Or setting something that runs at "system level" to restore normal mode (app opening should in turn delete this kind of service then)?

some ideas

[Wagnard]

Yeah I 100% agree with you. Idea of runOnce is already implemented and this run only when user log-on. The other thing that could work is the service and it will require some work to be done. The other option would be to completely remove this feature and let the user manually go into safemode. But lets be honest, I personally think that DDU is not really responsible if you loose your microsoft password heh?

[mirh]

But lets be honest, I personally think that DDU is not really responsible if you loose your microsoft password heh?

Well, technically let's say it was my cousin. Anyway, that was just an example. Who knows what's then :s

Anyway, I just now realize that Run is still executed after log in (just for any user instead of the current one). It seems there are still lots of other keys before that though. RunServicesOnce seems the most orthodox indeed.

[Wagnard]

We will look at this. the service thing is the most probable thing I will do.

[Wagnard]

According to this : https://support.microsoft.com/en-us/kb/179365 the "RunServicesOnce" is not working anymore :(

I guess this will end with a normal service that will be remove when DDU runs. I will also have to enable Safe Mode to actually load it. (usually safe mode is quite specific for what services loads.)

[mirh]

.-. I wonder if it wouldn't just be simpler to force the boot selection menu (aka "legacy mode" under W8/10 iirc) Albeit this way "100%" of people would be "affected", for as much of a simple click as it would be.

[Wagnard]

I already did that in the past and the user reception was not really happy about this... I wonder why tho...

[mirh]

Perhaps.. "time window" was too short? I mean.. if it was 5 seconds I could even miss the right moment to select safe mode

[Wagnard]

If I remember correctly, some users were lost and didn't know what to do :/

[mirh]

... the fuck? Monkeys would be able to select the right one.

[Wagnard]

Closed as we added a warning message before the user goes into safemode that their real password is required and that PIN does not work,

[mirh]

Mhh.. not exactly what I hoped, but whatever.

[Wagnard]

Yeah sorry, I know you would have liked to see the "F8" menu style but there is 1 issue that some users may had with this. I know some users who select to have this menu always by default. And there iis no way for DDU to know about this and after the cleanUP it would remove it to thoses users. I can already imagine the reports that DDU changed their preference etc. So I think for now a good and evident warning should be enough. But no worries, i'm still looking for a way to possibly set it back (safemode) to normal mode before login in.

[mirh]

According to this : https://web.archive.org/web/20160322121721/https://support.microsoft.com/en-us/kb/179365 the "RunServicesOnce" is not working anymore :(

I feel like I got hit by a truck of stupid. Did you try the hint of one of my OP links to prefix an asterisk or an exclamation mark to the command?