Conversation
Notices
-
Embed this notice
Eric Zhang 2: Episode 1 (eric@pl.starnix.network)'s status on Saturday, 07-Sep-2024 00:01:58 JST Eric Zhang 2: Episode 1 I GOT INTO FUCKING SAFE MODE -
Embed this notice
Pleroma-tan (kirby@lab.nyanide.com)'s status on Saturday, 07-Sep-2024 00:21:57 JST Pleroma-tan @eric @phnt shutdown /s /t 0 -
Embed this notice
Eric Zhang 2: Episode 1 (eric@pl.starnix.network)'s status on Saturday, 07-Sep-2024 00:21:58 JST Eric Zhang 2: Episode 1 @phnt YOO THIS COMMAND FINALLY WORKS LET'S FUCKING GOOOOOO -
Embed this notice
Phantasm (phnt@fluffytail.org)'s status on Saturday, 07-Sep-2024 00:21:59 JST Phantasm @eric That install is hosed. Windows doesn't have that much recovery options. You can unironically try running sfc /scannow which should fix corruption (usually doesn't) in the base Windows image and if that fails with some gibberish error code that tells you something like "recovery image corrupted", you can try to run one of the dism commands that rebuilds it. It's dism /Online /Cleanup-Image /ScanHealth to check for corruption and dism /Online /Cleanup-Image /RestoreHealth to fix the corruption. After that try running sfc /scannow again.
That should at least give you a bootable system back.
-
Embed this notice
Eric Zhang 2: Episode 1 (eric@pl.starnix.network)'s status on Saturday, 07-Sep-2024 00:22:00 JST Eric Zhang 2: Episode 1 I have absolutely no idea what I should do rn -
Embed this notice
Eric Zhang 2: Episode 1 (eric@pl.starnix.network)'s status on Saturday, 07-Sep-2024 00:22:01 JST Eric Zhang 2: Episode 1 LMFAO
-
Embed this notice