5 ms·

Reboot harder. > Update as of 10:30 UTC on 19 July 2024: We have received reports of successful recovery from some customers attempting multiple Virtual Machin

by terom 2y ago

Reboot harder. > Update as of 10:30 UTC on 19 July 2024: We have received reports of successful recovery from some customers attempting multiple Virtual Machine restart operations on affected Virtual Machines. > We've 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. https://status.cloud.microsoft/ https://status.cloud.microsoft/

deleted 2y ago
[deleted]
jayknight 2y ago
Any indication that this might work for physical computers?
- isjamesalive 2y ago
  My physical workstation (a Precision laptop) was affected and a single reboot fixed it. Most of my colleagues weren’t as lucky.
  - jayknight 2y ago
    I think I'm well past 15 on my laptop now. My desktop was unaffected, but I reach over and click restart every once in a while to see if something different happens.
    - trilbyglens 2y ago
      Sounds like a race condition that some systems hot and others don't
- canistel 2y ago
  Worked for me. Working for a few or my colleagues. Reboot again and again.
bitwize 2y ago
It's amazing how "Did ye try tairnin' it off and on again?" is still the best first-line advice.
- mym1990 2y ago
  Update to: "Did you try turning it off and on again...15 times?"
  - jowea 2y ago
    Important advice since normally I'd resort to percussive maintenance way before getting to 15.
baal80spam 2y ago
I'm not the one to bash Microsoft "just because", but this "up to 15 reboots" thingy reminds me that MS most likely doesn't know what's going on in their own damn OS anymore. Related picture - not long ago such a message would've been completely unacceptable, yet here we are. https://i.imgur.com/4rQLcb7.png https://i.imgur.com/4rQLcb7.png
- exe34 2y ago
  sounds like a race condition that you have a fair chance of recreating after 15 reboots?

by terom 2y ago

deleted 2y ago

[deleted]

jayknight 2y ago

Any indication that this might work for physical computers?

isjamesalive 2y ago
My physical workstation (a Precision laptop) was affected and a single reboot fixed it. Most of my colleagues weren’t as lucky.
- jayknight 2y ago
  I think I'm well past 15 on my laptop now. My desktop was unaffected, but I reach over and click restart every once in a while to see if something different happens.
  - trilbyglens 2y ago
    Sounds like a race condition that some systems hot and others don't
canistel 2y ago
Worked for me. Working for a few or my colleagues. Reboot again and again.

bitwize 2y ago

It's amazing how "Did ye try tairnin' it off and on again?" is still the best first-line advice.

mym1990 2y ago
Update to: "Did you try turning it off and on again...15 times?"
- jowea 2y ago
  Important advice since normally I'd resort to percussive maintenance way before getting to 15.

baal80spam 2y ago

I'm not the one to bash Microsoft "just because", but this "up to 15 reboots" thingy reminds me that MS most likely doesn't know what's going on in their own damn OS anymore. Related picture - not long ago such a message would've been completely unacceptable, yet here we are. https://i.imgur.com/4rQLcb7.png https://i.imgur.com/4rQLcb7.png

exe34 2y ago
sounds like a race condition that you have a fair chance of recreating after 15 reboots?