Windows cannot be upgraded on native boot VHD. Updating is OK, but when user tries to upgrade Windows, an error message is shown: “You can’t upgrade Windows on a virtual drive“. To upgrade Windows on native boot VHD, it must be attached to a virtual machine. After upgrade, virtual machine can be deleted, and user can now boot to VHD containing upgraded Windows.
There’s a new (hidden) capability for managing disks and volumes in the Settings app in Build 20175, but I can’t seem to make it work on my Dev Channel test PCs. I’m forked, so to speak (as I explain in detail in this story).
When I fire up my Lenovo X380 Yoga test machine this morning, I quickly realize that my backup drive is MIA. A quick investigation shows corrupt partition data, being recovered in MiniTool Partition Wizard’s Data Recovery tool right now.
I decide to spring US$200 for a 5 TiB 2.5″ Seagate drive and a double-high 15mm drive enclosure, thinking I will lose out on performance owing to its 5,400 RPM rotational speed. A comparison with a 7,200 RPM 2TiB drive comes out surprisingly well.
Before I start messing around with my production PC I always make sure I have a current backup. So why am I not surprised that my current backup is now on a drive that itself needs recovery? Sigh.
Even new Windows 10 versions may use the old-fashioned 5-partition disk layout because that’s how the Win10 installer did things until 1909 came along.
On newer hardware, you may find the new Win10 disk layout (puts the Windows Recovery partition in last place, after the Windows OS partition) showing up after installing CU KB4524570.
Needing screenshots of Windows Setup for a new tutorial, I accidentally noticed today that Microsoft has finally changed its default partitioning of the system disk to comply with their own partitioning guidelines. The title image above shows how Microsoft recommends a GPT disk be partitioned. Until recently, and still in Windows 10 versions 19H1 /
Last weekend, I saw a post on Ten Forums that really got my attention. A fellow member had been preparing a deployment image, and was wondering why his answer file simply did not work. Here’s an extract from the original post: I’ve followed tutorials on Ten Forums, Win10Guru, docs.microsoft.com, and many others. I’ve made my
Because Secure Boot blocks unrecognized software elements from loading during the boot process (before Windows starts running), it may interfere when you’re installing or updating boot-related software, firmware or drivers.