Looking for:
Inaccessible_Boot_Device after System Restore/Software Installation - Page 2 - Windows 10 Support.Dual boot with windows 10 and ubuntu 18 - Microsoft Community |
Windows 10 inaccessible boot device after installing ubuntu free download. Dual boot with windows 10 and ubuntu 18
Windows 10 inaccessible boot device after installing ubuntu free download. Dual boot with windows 10 and ubuntu 18
Windows 10 inaccessible boot device after installing ubuntu free download.Inaccessible_Boot_Device after System Restore/Software Installation
Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation. Thank you for writing to Microsoft Community Forums. This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup.
If you are able to see the partition, then follow the below troubleshooting methods, else contact any local technician because the partition in which you have installed Windows 10 might be corrupted while doing the partition. Modifications of the settings are at your own risk.
Before trying the below troubleshooting methods, remove all the external devices from the computer except the mouse and the keyboard. If you see a message asking you to "Press any key to boot from DVD," do so. Method 1 : Startup Repair.
If prompted, select the OS you want to perform a startup repair on. Note : Startup Repair can only fix certain problems such as missing or damaged system files.
It can't fix hardware failures such as a failing hard disk or incompatible memory. I did some bisection with system drivers and found that when I disabled atikmpag. Since my system did not work well without the driver, I decided to live with the issue and not use WSL 2. Today, after reinstalling Windows in another attempt to fix the issue, I found that it was fixed and I could boot with virtualization enabled. However, after installing the Virtual Machine Platform feature, as required by WSL 2 , my machine stopped booting again.
I updated to the Fast ring, build My uneducated guess is that having SVM and the Virtual Machine Platform enabled means something is triggered in atikmpag. I will attempt to debug the issue once my cable arrives in 2 days' time. I've spent many hours since my last post trying to find a successful combination of build version, updates taken or skipped, updating or not updating drivers on my own, and previously installing WSL 1 or not.
They all failed. In every combination I tried, I was left with a binary choice of enabling Virtual Machine Platform and not being able to boot, or not enabling it and not being able to use WSL.
Clearly many other users are in fact using WSL 2 successfully, leading me to wonder whether the issue is about a specific incompatible driver or other quirk on my machine; or is about a subsequent patch to Windows or WSL that has made it impossible for new WSL 2 users to get past the initialization stage. I am not savvy on debugging windows boot issues so do not know how to proceed further.
I'm open to suggestions. I'd also appreciate any tips if there are shortcuts that would speed up my testing cycle: right now each try is very painful, requiring multiple failed reboots to access safe mode, having to say "I forgot my PIN" because that process locks out the normal log in mechanism, and not being able to access the recovery command console because it will not take my password.
I've also filed this as a new issue via the feedback hub. Given it is reproducible on at least my machine I feel like someone in QA should confirm whether the documented install procedure works on a fresh install of build with the current applicable updates on at least some machines. Side note: the Gigabyte Aero 15 doesn't have an AMD processor, so that rules out the exact same root cause as mine, driver-wise.
I'd also appreciate any tips if there are shortcuts that would speed up my testing cycle. That let me boot when I installed VirtualMachinePlatform.
You could try the driver bisection method I mentioned in my earlier comment to diagnose if it's a driver thing, but it's very annoying and requires manual registry editing. Let me know if you're open to that and I can give you more details! That hack lets me survive the reboot following enabling VirtualMachinePlatform, which lets Windows complete its setup, and gets me access to the wsl console command.
This lets me enter the third command from the setup instructions set wsl default version to 2. But when I go to the Store after that and go to the Ubuntu page, it hangs on a spinning circle. I rebooted, re-enabled VT-X, but was right back at the hang on boot problem. Thank you for the offer! Having spent my weekend on this issue as it is, it's past due for me to return to current work, and that process does not sound quick. Maybe I'll try again next weekend.
Thanks, you save my day. I got the same issue in my T AMD. After enter bios and disable AMD virtualization. I can boot into windows. I'm running Windows 10 Home Version I used to have the same issue after turning Virtual Machine Platform on. Although, I should mention that I have received blue screen of death a couple times after doing this.
But I'm attributing that to my OS being in the fast track insider edition. I ran into this problem on the GeoBook , which is a Celeron N powered netbook. Doing wsl --install would put Windows into a seemingly unrecoverable state.
But WSL doesn't work, of course. I will probably try getting WSL1 installed instead, but I just wanted pass on this information in case it helps. I must add that I don't know exactly what has helped me to get here over an year after all those failing attempts. In case anyone's curious, here's a link to my original comment: comment. No changes to hardware, just a reinstall of Windows, and suddenly WSL2 is causing this error. I had the same problem and was able to find a workaround.
For me, it was probably due to the network driver. Windows 11 uses the 1. With version 2. You should be welcomed with a command prompt of ubuntu on your desktop now. Enter a username and password, if necessary, and close the session with "exit" in the command prompt.
If you dont see an ubuntu shell, open up cmd, type in "wsl -s ubuntu" followed by "wsl" and you should now be in an ubuntu shell. Create a user and password if necessary, otherwise close it with "exit" and close the cmd afterwards.
The vmmem process should now still run in the background for a few more seconds. I opened the task manager and waited until the process terminated itself. You'll have to turn a few windows features on - several times in my case so if you keep getting errors after restart just make sure they are activated. The ones you need to activate are:. Hopefully this helps! If you do get errors in the Ubuntu download, check for the error code in the troubleshoot section of the WSL documentation:.
I have to go into safe mode, then Windows will automatically undo the installs, then I can use my machine again. Edit: I tried installing components one by one. First, I tried WSL. That worked and rebooted just fine. It broke mine the first time too and I had to entirely reinstall operating system. Then I followed the guide and it worked but like I said, I did have to re-select some of the features I turned on after restarting because they would be turned off again after restart for no apparent reason - possibly conflicting features or one needs to be turned on before the other?
I don't know. IT will take a few tries and a few restarts so try different combinations, maybe one at a time or all together until you find that they are all on. It's only three features after all so it's not an infinite amount of possibilities. They will all remain on after restart eventually, so persevere! After the installation, I can only boot Ubuntu. My win 10 doesn't boot anymore. I have the result.
I do now have a windows boot option in my grub menu, but it does not boot correctly. Press any key to continue This worked for me, after running boot repair as in karel's answer — effel. Type these lines in the terminal one line at a time. Boot from a recovery CD. You should see this. After that, reinstall Ubuntu the same way. Emerson Hsieh Emerson Hsieh 6, 5 5 gold badges 37 37 silver badges 61 61 bronze badges. Oops, forgot about that.
Thanks for reminding me! Thanks for the Answer. I was able to boot windows again [Ubuntu's disc partition tool did not work. When i restart my computer now, GRUB is gone, and it default runs windows.
In my disc partition Utility there are 4 disks: 1. Should i delete them all? Should i reinstall Linux but use the partitions t — Mike. The 3 partitions you told me aren't empty, it's just Windows can't read them. If you only see OS C: , then those are Ubuntu partitions. You can delete them safely. And no. The stuff in those partitions are probably corrupted, so I recommend deleting and recreating the partitions if you want to install Linux again.
Boris Boris 1 1 silver badge 3 3 bronze badges. Boot-Repair will take care of this. Note: the partitions still exist. Karim Mokhtar Karim Mokhtar 71 1 1 silver badge 4 4 bronze badges.
Method1 1. Click on " Troubleshoot " 3. Click " Advanced options " 4. Choose " Command Prompt " 5. Now restart your computer Good if this works for you, if not then try Method2. Start terminal type sudo fdisk -l 3. Now type. Unmount partation previously mounted earlier. Remove the pendrive and reboot your pc.
Prashant Mishra Prashant Mishra 27 3 3 bronze badges. In step 5. It also displays the entries that are currently not in the BCD store. This screenshot shows all 4 commands together in step 5. Now save then run: sudo update-grub This should be fine to make Grub menu appears on every boot.
Maythux Maythux Here's a screenshot of what a correct installation looks like:. Alexei Martianov Alexei Martianov 5 5 silver badges 11 11 bronze badges. Open the terminal and run sudo fdisk -l to see where Ubuntu is installed. Reboot with sudo reboot. Damon Hill Damon Hill 31 4 4 bronze badges. Thank you, Karel! Solution sudo apt-get install mbr If the package got installed use following to write the MBR.
Stormvirux Stormvirux 4, 28 28 silver badges 35 35 bronze badges. No luck. Both solutions were followed by "boot repair", this and this are the result of it.
I don't see any change. Also note that, everything in Windows is accessible to Ubuntu, so if we want to do some hack, we can! Please suggest. Lets try another alternative of installing grub.
I recommend rescatux from supergrubdisk. They have videos on how to recover grub. So restore windows mbr like I said in the above post without boot-repair ,and try booting directly to Windows ,If it works we know the issue is with boot-repair else try booting with rescatux and repair the grub — Stormvirux.
I tried your solutions without using "boot-repair" and no luck. Note that when I run solution-2, nothing is printed on the shell unlike solution-1 where there is some output. Now I am trying "Rescatux" tool for a while, I downloaded its.
BUT how to start this software?? In all its tutorial they start with the software already ON which is bad for newbie.
Can you tell how to use it? Earlier, I had followed the same wiki for creating USB image, but then couldn't get the option for how to start? Or may be I haven't understood the article properly.
Can we have quick chat. Is the command you displayed harmless i. Then I can give a try from Windows command prompt. I don't know how to go to control panel because Win8 is not starting. Can you elaborate more about creating recover disk? I tried that option and it posted the message "Boot file successfully created", then shut down and restarted the PC but no difference. I ran repair as well. It seems that couple of "Cold shutdowns" of Win8 has put it into an undefined state. If you have any more pointers, it will be quite helpful.
Yeah that would be my opinion as well, the booting part seems to be correct, but theres some problem with windows. I am looking into it and will let you know if i get anything. In the meantime try searching for your problem on the Windows forums.. Show 5 more comments. Show 1 more comment. After Windows has been upgrade to April? But fail to boot into Windows
Comments
Post a Comment