Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on lemmy.world

14 replies

Donut
leminal.space

“We have received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage."

A lot of liberties taken with that headline.

52
SuperIce
lemmy.world

It's like those smart lights that you power recycle 7 times to reset

20
Vik
lemmy.world

Is anyone able to read the full article? Is this a boot loop OS detection feature?

13
PineRunereply
lemmy.world

I saw in another thread: sometimes upon booting, the updater has just enough time to grab the fixed update before BSOD so keep trying.

I saw some SysAdmin threads as it was happening say to boot into safe mode, navigate to the affected file, and delete it.

22
MajorHavocreply
programming.dev

boot into safe mode, navigate to the affected file, and delete it.

Yeah. That's the easiest, unless the drive is encrypted.

I imagine the folks going for the 15 reboots approach are doing so because it's easier than waiting in line for their IT help desk to deliver them their boot encryption key.

13
Revan343reply
lemmy.ca

it's easier than waiting in line for their IT help desk to deliver them their boot encryption key

Especially when the encryption keys are all stored on a Windows server that's bootlooped

3
Vikreply
lemmy.world

I haven't been affected by this personally, just curious at this point what the variables are hah

1
mkwtreply
lemmy.world

Sounds like a race condition in a kernel driver. Try it enough times and maybe you can get clear of it once without triggering.

20

You reached the end