Update workflows/operations/Windows/Uninstall Updates via DISM.md
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 4s
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 4s
This commit is contained in:
@@ -4,6 +4,8 @@ You may find that you have a machine that does not want to boot because of a rec
|
|||||||
!!! info "Triggering Recovery Menu"
|
!!! info "Triggering Recovery Menu"
|
||||||
Microsoft's own guidance is a little upsetting, because to trigger the recovery menu to appear, you generally have to let the device reach the Windows splash screen and forcefully shutdown / restart the device 3 times before it triggers. At the time of writing this, I am not aware of any other ways to trigger the menu to appear.
|
Microsoft's own guidance is a little upsetting, because to trigger the recovery menu to appear, you generally have to let the device reach the Windows splash screen and forcefully shutdown / restart the device 3 times before it triggers. At the time of writing this, I am not aware of any other ways to trigger the menu to appear.
|
||||||
|
|
||||||
|
You can circumvent this annoying workflow by simply booting from a windows installer ISO / USB and choosing "**Repair this PC**"
|
||||||
|
|
||||||
### Recovery Menu Navigation
|
### Recovery Menu Navigation
|
||||||
At this point, you will be presented with a blue menu with large buttons, and one of them will say "**Troubleshoot**" or "**Advanced**", from there, you should see an option for "**Command Prompt**".
|
At this point, you will be presented with a blue menu with large buttons, and one of them will say "**Troubleshoot**" or "**Advanced**", from there, you should see an option for "**Command Prompt**".
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user