Can a small hard drive be converted to gpt & can you format a virtual drive as gpt with secure boot on? It looks like Microsoft is going to require Uefi enabled not sure about secure boot though for upgrade. I think that why I am had issues with build 10049. I am not using windows 10 at the present in any form.
What on earth are you talking about? UEFI is not required, nor is secure boot.
I disagree Kari. A previous build worked without issue but for 10049 it wouldn't install or kept crashing after installed. Something has changed.
Hi there
No problem changing a small HDD / SSD to GPT but there IMO is no advantage in doing that - especially if it's say a small SSD (120 to 256 GB). Having a small MBR boot drive gives you the maximum flexibility.
A UEFI computer can boot an MBR drive though. SECURE boot is another thing entirely --currently it can be disabled (and should be if you are testing all sorts of OS'es)
I'm not sure but if you still have W7 as a boot system I don't think that some versions will allow a boot from a GPT drive although it can of course READ and WRITE to other GPT drives. (Might be wrong on that but I'm sure W7 and GPT had issues as boot drive).
Cheers
jimbo
Not everyone is having issue's at all. The only issue's I've personally had using all the Windows 10 build's since October were as follows. 1. In the early builds running them in VirtualBox until February when I got a bigger ssd, kept hogging to much of my old 256GB. ssd with 10 & 8.1 on it. 2.This one was my mistake with configuring Rufus, I didn't set the 1st step to GPT, so EFI wouldn't show up for my flash drive and SecureBoot didn't get turned on. I fixed that one and everything is fine.What I have noticed in both Windows 10 TP 10041 & 10049 is that 3DMark Advanced doesn't score better in those 2 builds than Windows 8.1 Pro does. **SIDE NOTE** Don't use Microsoft's USB/DVD Tool if your pc has a UEFI, you'll never get the EFI option for your flash drive or a dvd, thus no SecureBoot.
I wish I knew why it keep crashing 10049 or not installing either by vm or actual hard drive. The last time I tried it took over two hours to install 10049, then after installed it booted and ran for awhile, it crashed. I couldn't get the error message it rebooted to quickly. Same thing happen with the 32 bit install as well.
My hard drive is 500 gb but windows was installed on 125 gb partition? Should the partition be bigger? I am trying a experiment in vmplayer. I converted the virtual drive to gpt. 10041 installed without issue in the vm. Now, I will see if it crashes one upgrade to 10049.
Updated
Did install differently it is working so far. Haven't tried upgrading yet.
You may need to do a search for Mail, People & Calenadar. In both build 10041 & 10049 they don't work. You need to open PowerShell as administrator and enter the command you find in the search you did. Then open the non-beta Store and redownload the Mail, Calendar & People apps. As far as 10049 not installing disable your antivirus software. It can't be enabled during a os upgrade. Make sure your other software & drivers are up to date first, too.Also, make sure your ram timings are correct first in your uefi or bios.
If you already have Windows 10 build 10041 installed, the Mail, People & Calendar bug could be preventing the upgrade. Follow the instructions for PowerShell in build 10041, then redownload them in the store. Then retry the update to 10049. After 10049 is installed redo the PowerShell command and Mail, People & Calendar reinstall through the regular Store again.
