After installing Windows 10 (upgrade from 8.1) and after a second reboot, the 100MB "SYSTEM" partition shows up in Explorer as the f: drive. It cannot be hidden in Explorer - "Hide Selected Items" - prompts for administrator permission then Error 'the parameter is incorrect'.
In Disk Management the SYSTEM Partition does not have a drive letter assigned, and ALL options are greyed out.
None of the solutions I have found work, seemingly because the partition does not appear as a drive letter to the OS, only to Explorer. How can I hide it?
Can you show a screenshot of File Explorer?
it is usually impossible for a drive to have a letter in File Explorer but not in Disk Management.
A drive letter being present in File Explorer but not in Disk Management is a known weird side-effect of installing Windows 10 upgrade over a Windows 8 installation that was created using some "disk cloning" software. In particular, this effect is known to take place if the Windows 8 installation was created with Paragon HDD-to-SSD migration software.
Paragon software works fine in general, but still they are doing something wrong, which reveals itself when trying to upgrade a "cloned" OS to Windows 10.
I had the same issue and I found no credible solution for it, aside from clean-installing Windows 8.1 directly to SSD from scratch and then upgrading it to Windows 10.
- Open Admin Command (Win+X->Command Prompt (Admin)) then type:
- diskpart
list volume====> look for the Volume # that has the size of 100MB
select volume # =====> # found from list above
remove
exit
This should remove the letter for the 100MB EFI System partition.It's a glitch with upgrade.it is usually impossible for a drive to have a letter in File Explorer but not in Disk Management.
This worked perfectly.
- Open Admin Command (Win+X->Command Prompt (Admin)) then type:
- diskpart
list volume====> look for the Volume # that has the size of 100MB
select volume # =====> # found from list above
remove
exit
Many thanks Topgundcp.
For info: the NoDrives Registry entry did not work in this case.
Also, this was an Asus factory install of OEM Windows 8.1 so there should not be any ghosting software involved outside the factory.
That is correct, but the factory does clone these disk in bulk...This worked perfectly.
Many thanks Topgundcp.
For info: the NoDrives Registry entry did not work in this case.
Also, this was an Asus factory install of OEM Windows 8.1 so there should not be any ghosting software involved outside the factory.
Yes, of course .. I just made the comment for people like AndreyT who are interested in particular cloning software, to draw their own conclusions as to the source of problems on other machines. It was no accident that I used the words "outside the factory".That is correct, but the factory does clone these disk in bulk...
