F5F Stay Refreshed Software Operating Systems Unable to disable secure boot functionality.

Unable to disable secure boot functionality.

Unable to disable secure boot functionality.

Pages (2): 1 2 Next
M
MarioCovrigel
Member
195
07-09-2017, 12:02 AM
#1
You're facing an issue with Windows 10 installation on your Asus Prime B350+ motherboard. After consulting a Microsoft representative, they suggested disabling Secure Boot, but it seems unavailable in the settings. You might want to try alternative methods such as using a different USB drive, checking BIOS/UEFI settings directly, or contacting ASUS support for further assistance.
M
MarioCovrigel
07-09-2017, 12:02 AM #1

You're facing an issue with Windows 10 installation on your Asus Prime B350+ motherboard. After consulting a Microsoft representative, they suggested disabling Secure Boot, but it seems unavailable in the settings. You might want to try alternative methods such as using a different USB drive, checking BIOS/UEFI settings directly, or contacting ASUS support for further assistance.

F
FarmerMort
Junior Member
10
07-17-2017, 04:42 PM
#2
The problem is unclear. Disabling secure boot isn't necessary and may cause issues.
F
FarmerMort
07-17-2017, 04:42 PM #2

The problem is unclear. Disabling secure boot isn't necessary and may cause issues.

C
CangarooKo
Junior Member
5
07-20-2017, 10:08 AM
#3
You just got your new PC built without an OS on the SSD and HDD. You tried installing Windows 10 on the SSD using a USB created with Microsoft Media Creation Tool, but you encountered a blue screen with a kernel error message. Some advice suggests disabling legacy support and secure boot, but you're unsure how to proceed.
C
CangarooKo
07-20-2017, 10:08 AM #3

You just got your new PC built without an OS on the SSD and HDD. You tried installing Windows 10 on the SSD using a USB created with Microsoft Media Creation Tool, but you encountered a blue screen with a kernel error message. Some advice suggests disabling legacy support and secure boot, but you're unsure how to proceed.

K
KaanVDB
Junior Member
10
07-21-2017, 11:02 AM
#4
K
KaanVDB
07-21-2017, 11:02 AM #4

S
Skywonder216
Member
171
07-22-2017, 01:37 PM
#5
Windows identifies storage devices by checking their characteristics and signals, even if they appear empty.
S
Skywonder216
07-22-2017, 01:37 PM #5

Windows identifies storage devices by checking their characteristics and signals, even if they appear empty.

D
damojosh
Member
200
07-26-2017, 09:53 PM
#6
Are these new storage options? If the previous setup used an MBR, it's likely the drives seem blank yet hold a boot file. I'd like to run a check. Disconnect both hard disks from the system then connect the USB drive and restart the computer. Do you receive the identical error notice?
D
damojosh
07-26-2017, 09:53 PM #6

Are these new storage options? If the previous setup used an MBR, it's likely the drives seem blank yet hold a boot file. I'd like to run a check. Disconnect both hard disks from the system then connect the USB drive and restart the computer. Do you receive the identical error notice?

E
EJThatGirl
Junior Member
45
07-29-2017, 02:32 AM
#7
The SSD arrived sealed, while the HDD had bubble wrap. Both turned out empty—confirmed via Linux USB check.
E
EJThatGirl
07-29-2017, 02:32 AM #7

The SSD arrived sealed, while the HDD had bubble wrap. Both turned out empty—confirmed via Linux USB check.

K
Koorok
Member
50
08-08-2017, 01:28 PM
#8
If the HDD had an MBR installation, a boot record might remain in the FAT. Disconnecting both drives helps verify if your USB drive is starting correctly. It's possible the USB wasn't made properly, which could be causing the issue. Try disconnecting both drives again and attempt to boot the USB installer. Does the same error appear or does it work?
K
Koorok
08-08-2017, 01:28 PM #8

If the HDD had an MBR installation, a boot record might remain in the FAT. Disconnecting both drives helps verify if your USB drive is starting correctly. It's possible the USB wasn't made properly, which could be causing the issue. Try disconnecting both drives again and attempt to boot the USB installer. Does the same error appear or does it work?

O
OzoneSkill
Junior Member
33
08-09-2017, 01:43 PM
#9
Both SATA cables remain problematic even after disconnecting them; you might need to turn off Fast Boot or similar settings.
O
OzoneSkill
08-09-2017, 01:43 PM #9

Both SATA cables remain problematic even after disconnecting them; you might need to turn off Fast Boot or similar settings.

A
Aragone
Member
224
08-09-2017, 05:06 PM
#10
No, your USB drive isn't functioning properly. Did you use the official Windows Creator tool? Were there any issues or errors?
A
Aragone
08-09-2017, 05:06 PM #10

No, your USB drive isn't functioning properly. Did you use the official Windows Creator tool? Were there any issues or errors?

Pages (2): 1 2 Next