Installation :: Turning Off Secure Boot / Fast Boot Required?
Apr 29, 2015
As I get ready to do a clean install of 10074 I am curious about the need to disable secure boot and fast boot options. If I do disable secure boot do I need to enable legacy boot?I have had limited success with previous installs to a 2nd hard drive and the problems that arose always seem related to dual booting.
In one instance I did a clean install of 10061 and had left secure boot enabled. In order to get dual boot working I had to disable secure boot, and upon rebooting I needed to change it back to secure. I then made Win 8.1 the default boot and then Win 10 would never boot from the menu, it would just take me back to the boot menu and I could boot into Win 8.1.
will one have installing Windows-10 on a machine now running Windows-7 64-bit with an older BIOS? In particular, the BIOS setup area has no references to UEFI. So, references to "disabling Secure Boot" don't make sense. (I have a DELL Vostro 1500, bought in March 2008, which is still very functional.)
Basically, I have a really bleepty BIOS that will only let me change the boot order with secure boot disabled and legacy boot enabled. I need secure boot because I just installed windows 10 onto a new drive and it won't activate. I have heard that this has something to do with secure boot being disabled. I still have the activated drive, which is the primary drive. Is there anything I can do to change the boot order?
Control PanelAll Control Panel ItemsPower OptionsSystem Settings
Unchecking the "Turn on Fast Startup" command in the above setting path does not do it. There is supposed to be a motherboard software for enabling a normal startup the next time the computer is restarted.
I installed Windows 10 Pro on an Intel NUC5i3RYH. In the UEFI settings I enabled Secure Boot, enabled UEFI boot and disabled Legacy Boot, yet in Windows 10 System Information it still says Secure Boot State: Off.
Is there something else I need to do to get Secure Boot working?
i had secure boot up and running on my windows 8.1 machine after a clean install, but now since Microsoft upgraded me to windows 10 it seems as my secure boot is off again, but it's enabled in my bios is so weird, it's enabled in bios but off in windows 10? Is not much of a big deal to me in a since but just wondering why it still shows as on in bios but off in windows 10.
I was updating my Dell Venue Pro 8 to Windows 10 Build 10547 and got a red error message that read. "Secure Boot Violation" "Invalid signature detected. Check Secure Boot Policy in Setup". There is an OK button at the bottom of the message, but nothing happens when I try to click on it. I can shut the tablet off, but when I start it I get the same message. I am stuck. Where to I go from here.
I just canceled my Windows 10 download request because of "Secure Boot." I find it's very disturbing to work under its conditions of inflexibility. Without an option to select or deselect, Secure Boot is an irrational restriction on the individual.
I have a new configuration (z170 chipset, i3-6320, fast SSD) for my desktop and it boots slower than my laptop (Acer V3-574G (i7-5500) with the same SSD as my desktop). I don't think the i3-6320 vs i7-5500 can explain such difference.First thing is that Hibernation and Fastboot are activated but not working on my dektop PC: command "Get-WinEvent -ProviderName Microsoft-Windows-Kernel-boot -MaxEvents 10 | Where-Object {$_.id -like 27}" gives me 0x0 (cold boot from full shutdown). Parameters ares ok in settings and in registry (hiberboot = 1).I tried using Fast boot and MSI fast boot in the bios: no effect. I tried to enable win10 whql in bios but it is disabled after rebooting, with a warning message saying that my graphic card does not have GOP.So, I'm not able to fast boot due to an "old" hd7750 graphic card ?
So I just upgraded my wife's computer and noticed it loads directly to my account which has no password. When I restart it never asks who's account I want to logon to, just goes to mine. Of the three computer I've upgraded this is the first to do this. Also in the power options I can't find the option for fast boot.
Laptop is Lenovo X220 that had Windows 7 Pro and upgraded to W10. It has had already 5 vanilla installs of 10 Pro 1511 on it.
2x install with an old 3.5" 5400 RPM stock HDD drive and the 4-5th and final install with an upgrade to an SSD. The HDD was changed to SSD because of me thinking the HDD was dead and was causing the computer to lock up at boot.
Tried 3 different operating systems on the machine as well, Windows 7 (no problems) (stock with computer), Windows 8.1 (with Fast Boot) enabled and no problems on Windows 8.1 O/S and finally W10 PRO 1511, vanilla from Microsoft directly.
For some reason after W10 installs, does its updates, reboots, drivers are updated and everything seems fine after a couple of reboots and such. Works normally, wakes up from sleep. Only 3 programs get added. Firefox, Chrome and WinRar.
After that shutdowns OK, but when she boots up it gets past the welcome screen and hangs on the desktop. Complete hang everything becomes unresponsive, but the mouse pointer. I can dance the pointer around but No keyboard input no GUI input, nothing. Only way to come out is with a POWER BUTTON DOWN. Was trying to solve this issue since December and never found any solution, thought it was drivers or internet, or hardware but nothing, no dice. Even if it didn't connect to the internet after install and a program or 2 were added via USB and I shut down it would hang upon next boot.
So I did reading and reading and researching and I came upon a thread that mentioned W10 hangs on welcome screen with Fast Boot on, I thought no this can't be it because I make it past the welcome screen. I hang on the desktop when I'm actually in Windows. I can manage to click Start button and the system will hang. Only way to get it to respond is to hold down the power and power it down. Temps seem OK, MEMTEST came back fine, replaced HDD with SSD, only other thing I could think out was drivers or hardware (mobo) failure or something else ....
Then I decided to clean install update drivers via Internet, reboot and then disable FAST BOOT via @Brink regedit hack, because for some weird reason, on this machine on every clean install, FAST BOOT IS NEVER SHOWED in the POWER menu. I could not understand this. I do not have this option at all like @Brink has in his diagram photo. The option is just not there!!! But the registry though the hiberbootenabled value is set to "1".
So two questions, why is it checked and greyed out (that I cannot uncheck it) and 2, the only way I was able to change the value was manually via @Brink registry edit.
OPTION 2 - using a bat file because option 1 was unavailable. Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums
Once I disabled FAST BOOT, the laptop has been fine since. No locking up anymore period!
SSD is 850EVO and W10 PRO is the only O/S on the machine, legit with digital entitlement upgraded from W7 PRO key on the Lenovo, because its an X220 thinkpad so 'business' series. No problems since.
#1 Fast Boot option to disable on startup is not avialable on the machine? Value is "1" in registry but cannot make changes to it via control panel as it simply is just not there. (This was the case with both HDD and new SSD). Windows 8.1 shows the option, not 10.
#2 Hangs on startup after welcome screen
#3 Only way to prevent is to run the .bat file from @Brink or manually edit value in regedit, save, exit, shutdown, go on with life.
AFAIK value in REGISTRY is set at '0' and machine works ....
Brink has this option on his machine via control panel but I do not on the laptop. Brinks:
My PC does not give me that option at all. Is if it doesn't even exist.
I've been in the Windows Insider program since it started, getting every new build, and I usually hibernate my PC to keep all my apps open, only rebooting for updates that need it.
This has been fine on Windows 8, 8.1 and 10, up until the November update. I downloaded the initial, "faulty" November ISO with the media creation tool, but didn't get round to installing it until after it'd been pulled and reinstated. So I used NTLite to integrate that update in to the ISO I already had and did a clean install of that.
Everything was great until the next morning when I turned it on again. It booted as normal until it got to the Windows boot screen, which flashed on screen for 1 second or so before the PC just instantly powered down, like someone had pulled the plug out.
I troubleshooted this for ages and eventually worked out it's hibernation and fast boot - the only way to make the PC boot properly again is to go in to the BIOS and change the amount of memory given to the integrated GPU so you're effectively changing the hardware of the machine, which makes Windows dump the hibernate images and boot from scratch.
I've been reading that having fast startup on in windows 8/10 can cause issues with dual booting systems with other operating systems installed like windows 7. I have windows 7 on one ssd and going to have windows 10 on a second. Will i have to disable fast startup in windows 10 or any other type of hibernation settings.
Installed MSI's "Fast boot" software, upon restarting every time I am greeted with a bluescreen mentioning it not detecting a device.
MSI Fast boot also seems to increase the time it takes for the mouse and keyboard to start so when it asks "Press enter to Retry, or F8 to change settings" i cannot do anything as the keyboard and mouse are not on.
In my desktop I have two hard disks ( disk 0 and disk 1 ) . Disk 1 is a clone of disk 0 created by Macrium Reflect Disk 0 : ( C: ) windows 10 pro , upgrade from windows 7 , ( E: ) windows 8.1 pro , ( G: ) Storage partition Disk 1 : clone of disk 0
problem description : I see in msconfig / boot a wrong listing
windows 10 ( C:WINDOWS) : Current OS ; Default OS
windows 8.1 pro ( H:WINDOWS ) instead of ( E:WINDOWS )
Nevertheless the dual booting works fine as well as the shift between the disks via BIOS.
The question is , could I fix the situation using the EasyBCD of Neosmart Technologies to edit the bootloader ?
I see can change drive letter H: to E: and save the change , am I right or wrong ? or any other way ....
My laptop has dual boot - Windows 7 and Windows 10. My Win7 environment is my main working environment with lots of programs installed and important files. I installed the Win10 environment just to play around with 10 during the technical preview. Now, I would like to disable the 10 environment and upgrade the 7 to 10. Am I able to do this, or have I already "used up" my one upgrade on this computer's Windows license?
I notice that in Windows 7 I have not received the icon in the notification area that invites me to upgrade to 10. This makes me think I might have used up my chance to upgrade.
My end goal is to have a single Windows 10 environment. Note that the reason I want to upgrade my 7 environment to 10 is because I don't want to have to re-install all of my programs and files into the current 10 environment.
I'm making a image for installation of windows 10. I make a USB flash drive with WINPE. and once the device starts into WINPE, it will automatically start to install windows 10 by calling "dism /apply-image". Normally i just shutdown the computer after installation, but now i want to reboot the device and boot into the windows i just installed. But i can't, because if i reboot the device, it will boot into WINPE again and start another turn of installation of windows. How could i temporary boot into my windows 10?
After several weeks of testing I'm ready to go full on Windows 10 and want to get rid of Windows 7 but I have some partitioning issues I want to clean up. I currently have Windows 7 on drive 0 (360 GB) and Windows 10 on drive 1 (500 GB). Both are SATA drives and RAID is enabled in the bios but not active.
What I think I'd like to do is simply swap the drives physically so that Drive 0 has my current Windows 10 install on it and make it primary boot active etc. The drive with Windows 7 on it would become drive 1 and I would delete the Windows 7 partition and re-partition it with a clean empty partition just for extra space.
Second question, any advantage to using this drive configuration in a RAID setup?
I have a legacy 64 bit dual core desktop (ASUS mobo). I have several Sata hard drives in it with the 4th partition of my 1 Terabyte drive containing my Windows 10 Professional boot OS. After converting another similar legacy machine to a NAS device I took the old Windows 10 32 bit OS drive from it and tried booting the ASUS machine with it. Needless to say, the OS didn't like it and reverted to Windows 10 Pro Insider Preview edition (build 11082).
When I tried to restore the boot drive to the original one for this machine the master boot was missing.
I had just formatted another partition on the same drive that had contained a Windows7 installation that had failed. This partition may have contained the master boot record. So I booted to a command prompt from a USB drive and successfully ran the following commands:
bootrec /RebuildBcdbootrec /fixMbr bootrec /fixboot bootsect /nt60 SYSbootsect /nt60 all
After that the BIOS just says "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system" This disk and OS are on the original machine it used to run on. As I understand it, Windows 10 tries to record it's key to somewhere in the BIOS. But the BIOS on these old machines don't provide such a facility. I don't understand what Windows 10 OS does with the key in this instance. If it was recorded in the BIOS then I'd presume that the other Windows 10 drive I attempted to use would have found it and used it. Or perhaps not, since it didn't like the new environment.
what I'm looking for is a way to get my original Windows 10 to boot again on the same machine it had always work on before, from the 4th partition of the 1 terabyte drive I'm using.
I wasn't sure which forum to put this into. I created a backup image on a usb hard drive. I wanted to be able to restore it using a usb recovery thumb drive. I used the create usb recovery tool and created the recovery flash drive. When I try to boot from the flash drive I get an error saying that the boot configuration data is missing or contains errors. I can boot up the laptop using the current windows install so it isn't referring to the hard drive. I have tried several usb drives and get the same message on each. Here is a screenshot of the message.
After installing a 32 bit windows 10 from a USB by mistake I decided to upgrade to the 64 bit version. I have 3 hard drives, one of which is an ssd that I am trying to install the OS to. After downloading and setting up the media creation tool and creating a USB I restarted and boot form USB.
I followed the steps and deleted the existing windows 10 partitions on my dad and tried installing straight to the unallocated space. After the installation completed it restarted the installer, which is not what happened when I previously successfully install windows 10. I then changed the boit order to have my ssd first and rebooted, which gave me the Reboot and select proper boot device or insert boot media error.
Confused I loaded up the installed and there were correctly partitioned installs already on the ssd ( although one partition looked a little small). I tried reinstalling windows 10 with the same result over and over.
When I try to boot from a recovery flash drive, it fails with: EFIMicrosoftBootBCD error status: 0xc000000f and message: The Boot Configuration Data for your PC is missing or contains errors.
The recovery flash drive was created on a Lenovo ideapad originally with Windows 8, now upgraded to Windows 10, latest upgrades applied. Checked the box for copying system files. Target drive was a 16GB DataTraveler flash drive formatted as FAT32. Creation ran to completion with no errors. When booting normally, Windows 10 runs fine with no issues. I tried re-creating the recovery drive with the same results.
I created a repair disk and tried to use bootrec to fix the issue, but I suspect it did nothing or fixed the c: drive. I ran boot rec while in the root directory on the flash drive.
I used MicroTool partition manager to delete the extra partitions on an OS drive with win10 (leaving just the main C partition on the drive), and now the laptop will not recognize the SSD with the OS on it, and obviously cannot boot. I also tried using the bootable partition recovery tool from MicroTool, but restoring the partitions also does not work, it will only allow one of the two partitions to be restored.
Today I installed Windows 10 on my machine (ASUS N55SF laptop) for the first time on a separate hard drive. Now I have Windows 7 on my main hard drive and Windows 10 on my new drive (the latter being an SSD one). After installing Windows 10, I got a new boot option in my BIOS called "Windows Boot Manager" which is set as default, but it runs Windows 10 directly, I can't see any boot manager (I can assure "Windows Boot Manager" behaves this way because my BIOS lets me override the boot option, so that I can directly run any boot option, and this is probably the only way I can run Windows 7 currently).
If I go to Start → Advanced system settings → Startup and Recovery → Settings, I only see Windows 10 in the "Default operating system" drop-down menu, while I only see Windows 7 if I do this while on Windows 7. It's like the two OSs are not completely aware of each other.
Over the weekend I upgraded from 8.1 (which was working perfectly) to Windows 10. Unfortunately, it had a few problems - namely that it would 'hang' at random intervals (5 minutes to 5+ hours). In an attempt to isolate what was causing this, I was advised to use Msconfig to do a clean boot.
Unfortunately, in the process, I have rendered my PC near-useless, as I accidentally ticked the box "Use original boot configuration" under Selective startup. (I know, I know. I'm so cross with myself.) As a result, I am now presented with what looks like my old boot screen - offering Windows 7, Windows 8, Windows 8.1, Windows 8.1 with Media Center, but no Windows 10.
(I originally had Windows 7 on what is now my D: drive. I ended up dual booting with this and Windows 8, but I'm pretty sure the version of 8.1 - which I've just upgraded to Windows 10 - was a clean install. It's certainly on my SSD (C: drive).)
Anyway, by using Change defaults... - Choose other options - Troubleshoot - Start-up Settings, I was at least able to bring up the screen that gives you Safe Mode as an option. This allowed me to boot into Windows 10 Safe Mode.
I went back to MSConfig and eventually found a way to deselect 'Use original boot configuration' (it was greyed out for a while). However, on restart, it still showed me the old options, i.e. no sign of Windows 10 Pro. It seems the only way I can currently boot into Windows 10 is via Safe Mode.
I've tried various things today - I tried to use Bcdedit to force it to look at the C: not D: drive, and I've tried booting with a Windows 10 DVD and using the Repair option (but partway into the repair process it starts thinking it's a Windows 8 machine again...).
I've just 'spoken' to a chap at Microsoft and he is adamant that there's no alternative (because there's no Refresh option under Settings - Update & Security - Recovery) but to reinstall Windows 8.0, and then upgrade to 8.1 and then Windows 10. As you can imagine, I really, really don't want to go down that route. But, at the moment, I can't even roll back to 8.1.
Given that I can still - sort of - boot into Windows 10, the correct MBR/BCD/whatever must still be on my C: drive somewhere, surely?
