The following section doesn’t match the picture.
- Start Registry Editor, and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorAV\
It’s supposed to be iaStorV, and iaStorAV has no key / values or child under the tree.
1 Like
Yes, thank you, this is a typo.
I am trying to follow this guide that you have kindly provided. I have gotten as far as diskpart.
I did “list volume” and found that the windows partition is volume 0 and already has the letter C assigned to it.
So I did “select volume 0” and then “activate”.
It seems that DISKPART does not know the “activate” command. It has the command “active”, but when I try this, I get the response “The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks.”
I am unsure how to proceed. Any help would be much appreciated.
@maria.jensen Hi Maria, first you spotted a typo, thanks. Second, I should have been clearer, and there’s no reason for the active command. This is only relevant for non-UEFI systems. I will amend the tutorial, and you can proceed without it.
1 Like
Folks,
Please remember that the purpose of this thread is to improve the documentation.
It was not really intended to be a support thread.
Wherever you find your answer, please come back and make specific recommendations to improve the strings and images of the documentation to save other users the hassle you encountered.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorAV\ should be HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorV\, and can be confirmed by the accompanying screenshot on the help page.
I tried “active” which is the correct command, but it said something about the volume not being Fixed MBR. So that didn’t work for me either. It should be changed.
1 Like
I found the same thing today. When does the actual webpage get updated?
I found a workaround to boot windows after changing to AHCI easily.
I wasn’t able to make it work (no troubleshooting in the page worked) until I manually setup a safeboot minimal mode with an elevated cmd right after I changed the registry values.
Apparently the regedit changes for the “ RST enabled, Windows installed” scenario were being reset on the first fail cycle, so when entering repair mode they wouldn’t get loaded. I’ve read somewhere that the StartOverride changes only lasts for one boot cycle.
The solution was to set the safe mode (safeboot) manually. Right after the regedit changes:
- With a cmd with admin rights (windows search: cmd, then right click, run as admin):
bcdedit /set {current} safeboot minimal - Reboot to BIOS.
- Change from RAID (RST) to ACHI in the BIOS.
- Reboot.
- Windows enters safe mode correctly and setups the “new” hardware using the temporarily enabled drivers. New hardware connected sounds and all.
- Then before restarting, revert the safeboot mode:
bcdedit /deletevalue {current} safeboot - To go back to normal boot.
Tested with a Dell XPS 13 7390 (model P82G)
Also found a typo: The activate diskpart command should be changed to active (and add a note that it might fail with an error message about the volume not being “Fixed MBR”)
15 Likes
That’s a good question. The actual webpage is a static HTML page, which I committed at the request of @igorljubuncic. But there is no good procedure in place yet for maintaining it.
Myself don’t know the topic. Possibly, if you would submit a merge proposal with obvious things like typos, I might be able to merge it (it’s this Bazaar branch). But I have a feeling that the changes you would like to see are bigger than that, and if so they need to be reviewed by somebody with sufficient knowledge.
Yes.
Agreed.
Unluckily I’ve never used bazaar and it would take too much of the company’s time just to fix two typos.
The change proposal is to manually enable safeboot right after the registry changes, which reset each boot cycle by design, to avoid the failed boot (prior to the repair one) resetting them. Or at least that’s the working theory.
EDIT: Apparently reading further I ended up in this specific guide for my laptop model which does something similar (although not through command line but via the msconfig app)
https://wiki.ubuntu.com/Dell/XPS/XPS-13-7390-2-in-1
Maybe the msconfig approach is easier on the user and to add to the RST guide.
Thank you, man!! Thank you very much.
@igorljubuncic can you add this to the post, please?
Happy, I found this right before editing Bcdboot.
Asus ROG Strix G17 G712LWS-WB74 with UEFI, GPT, Intel RST
1 Like
Hi. I just wanted to make you aware that tutorial from this post does not work at all for me (Dell Latitude).
- Changing registry in Windows didn’t help (Windows didn’t boot)
- While trying to repair Windows: none of
bcdedit /deletevaluecommands worked. Error:
An error occurred while attempting to delete the specified data element. Element not found.
- Bcdboot section: none of the two configurations describe volumes on my device (I’ve got Windows freshly installed, no changes on disk after installation). I’ve got one C volume (with Windows), one volume NFTS 508 MB and one FAT32 100 MB.
- None of those volumes contain
bootfolder I couldcdinto.
To sum up: hardly any steps from this tutorial worked as expected. Moreover, you’ve got even more outdated version of it here: Intel RST (containing non-existent commands like activate). This is the link Ubuntu propose to user when installation fails due to this storage incompatibility.
I suggest you either fix this post or delete it, because it doesn’t help anyone and create confusion to users how want to install Ubuntu.
1 Like
Worked flawlessly on my Acer A515-55G. Thanks!