Can you try booting and installing WIndows 11?
Computer will boot from USB TO LINUX but not USB to windows
** I am resposting this from Asus help site as I still haven't found a solution** Hello. First off I'm new! I built a computer from scratch last year. I have the Asus x570 gaming motherboard. I installed windows 11 a few weeks ago and it has been running fine. Last week, it green screened and now I can't get it to boot to windows no matter how I try. I'm at a loss, I keep thinking there is something I can do other than send my motherboard back, but no one has any advise that has worked yet. I've included a video that, is the problem. Has anyone had issues? Or suggestions. Ive now disconnected all drives but my main m2 drive, I have windows bootable in there. I've tried booting legacy. And uefi. I just don't know what else to do! Things I've tried...
- Checking ram sticks
- Flashing bios
- Upgrading bios
- Taking all drives out and just booting windows from USB
- Legacy and non legacy boots
- Iso of win 10 from RUFUS
- BOOTING UEFI from usb drive and installing windows that way
No matter what I try, it just sits on the window square screen.
ALSO it will let me boot just fine to a Linux USB without an issue. video
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
51 answers
Sort by: Most helpful
-
Anonymous
2021-10-15T19:21:27+00:00 -
Anonymous
2021-10-15T18:38:09+00:00 I honestly don't know if this will help but this is from a boot repair program on Linux... this is showing all my drives.
boot-repair-4ppa130 [20211015_1316]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/nvme0n1.
=> No boot loader is installed in the MBR of /dev/sda.
=> Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector
2949431296 of the same hard drive for core.img. core.img is at this
location and looks for (,gpt5)/boot/grub. It also embeds following
components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_gpt biosdisk
---------------------------------------------------------------------------
=> Windows 7/8/2012 is installed in the MBR of /dev/sdc.
nvme0n1p1: _____________________________________________________________________
File system: ntfs
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi
sda2: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 8 or 10
Boot files: /Windows/System32/winload.exe
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system:
Boot sector type: -
Boot sector info:
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb3: __________________________________________________________________________
File system: BIOS Boot partition
Boot sector type: Grub2's core.img
Boot sector info:
sdb4: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: According to the info in the boot sector, sdb4 starts
at sector -1345533952. But according to the info from
fdisk, sdb4 starts at sector 2949433344.
Operating System:
Boot files:
sdb5: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 20.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
sdc1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/boot/bootx64.efi /efi/microsoft/boot/cdboot.efi
/efi/microsoft/boot/cdboot_noprompt.efi
/efi/microsoft/boot/memtest.efi /bootmgr /boot/bcd
================================ 3 OS detected =================================
OS#1: The OS now in use - Ubuntu 20.04.3 LTS CurrentSession on sdb5
OS#2: Windows Recovery Environment (boot) on sdc1
OS#3: Windows 8 or 10 on sda3
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.11.0-38-generic root=UUID=28fcfd08-e98e-4232-a2ea-9f6a189ede2c ro quiet splash vt.handoff=7
===================================== UEFI =====================================
BIOS is EFI-compatible, but it is not setup in EFI-mode for this installed-session.
3ff213addd49e6515922de34952223ad sda1/Boot/bootx64.efi
3ff213addd49e6515922de34952223ad sda1/Microsoft/Boot/bootmgfw.efi
b8736f6dbf1baf951d389be5a519fb32 sda1/Microsoft/Boot/bootmgr.efi
ae8af199ef80311f9cee9de104a15496 sdc1/boot/bootx64.efi
1309af23db7b4cdd16bb29b41d6975e5 sdc1/microsoft/boot/cdboot.efi
ba914e4bb811a1b27220f020d2672167 sdc1/microsoft/boot/cdboot_noprompt.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sdb : is-GPT, hasBIOSboot, has-noESP, not-usb, not-mmc, has-os, 34 sectors * 512 bytes
nvme0n1 : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, 2048 sectors * 512 bytes
sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
sdc : notGPT, no-BIOSboot, has---ESP, liveusb, not-mmc, has-os, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sdb5 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, farbios
nvme0n1p1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdb2 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdb4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda3 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sda4 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdc1 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
Partitions info (2/3): _________________________________________________________
sdb5 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdb2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdb4 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda3 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot
sda4 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
sdc1 : is---ESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, bootmgr, is-winboot
Partitions info (3/3): _________________________________________________________
sdb5 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sdb
nvme0n1p1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, nvme0n1
sdb2 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdb
sdb4 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdb
sda1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda3 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sda4 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
sdc1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdc
fdisk -l (filtered): ___________________________________________________________
Disk nvme0n1: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 50030725-0C93-428D-AF8E-F5986DD9F030
Start End Sectors Size Type
nvme0n1p1 2048 1953523711 1953521664 931.5G Microsoft basic data
Disk sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: B3E47A00-920F-47A1-ABE5-FBE04A9845FE
Start End Sectors Size Type
sdb1 34 32767 32734 16M Microsoft reserved
sdb2 32768 2949430332 2949397565 1.4T Microsoft basic data
sdb3 2949431296 2949433343 2048 1M BIOS boot
sdb4 2949433344 2950483967 1050624 513M Microsoft basic data
sdb5 2950483968 3907028991 956545024 456.1G Linux filesystem
Disk sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: 2E271F1B-4E02-41C3-886A-2781F0F9DF31
Start End Sectors Size Type
sda1 2048 206847 204800 100M EFI System
sda2 206848 239615 32768 16M Microsoft reserved
sda3 239616 975726701 975487086 465.2G Microsoft basic data
sda4 975728640 976769023 1040384 508M Windows recovery environment
Disk sdc: 57.63 GiB, 61865984000 bytes, 120832000 sectors
Disk identifier: 0x0bef4ffb
Boot Start End Sectors Size Id Type
sdc1 * 2048 67110911 67108864 32G c W95 FAT32 (LBA)
parted -lm (filtered): _________________________________________________________
sda:500GB:scsi:512:4096:gpt:ATA CT500MX500SSD1:;
1:1049kB:106MB:105MB:fat32:EFI system partition:boot, esp;
2:106MB:123MB:16.8MB::Microsoft reserved partition:msftres;
3:123MB:500GB:499GB:ntfs:Basic data partition:msftdata;
4:500GB:500GB:533MB:ntfs::hidden, diag;
sdb:2000GB:scsi:512:512:gpt:ATA CT2000MX500SSD1:;
1:17.4kB:16.8MB:16.8MB::Microsoft reserved partition:msftres;
2:16.8MB:1510GB:1510GB:ntfs:Basic data partition:msftdata;
3:1510GB:1510GB:1049kB:::bios_grub;
4:1510GB:1511GB:538MB:fat32::msftdata;
5:1511GB:2000GB:490GB:ext4::;
sdc:61.9GB:scsi:512:512:msdos:General USB Flash Disk:;
1:1049kB:34.4GB:34.4GB:fat32::boot, lba;
nvme0n1:1000GB:nvme:512:512:gpt:WDS100T3X0C-00SJG0:;
1:1049kB:1000GB:1000GB:ntfs::msftdata;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 5E17-2281 f527b3b0-aa6f-4c41-ae52-257221ae7f88 EFI system partition
├─sda2 75908e0a-f6ee-4d6d-b4ea-dc14917e2ad8 Microsoft reserved partition
├─sda3 ntfs 5098236C98234FB0 775add46-3d43-40f0-a7c9-c4d04175c9af Basic data partition
└─sda4 ntfs 12B838C6B838AA5D 32150035-0ca1-4bf6-bf7a-e8b6aea88161
sdb
├─sdb1 5e10bcee-c64c-4fcd-91a9-f91864d13988 Microsoft reserved partition
├─sdb2 ntfs DE4E551E4E54F0AF 6b986f8d-64df-4e8c-9bcd-2e8b47df6a7f SSD Basic data partition
├─sdb3 47c5c455-9ff3-4c70-b8c4-8b36bd664c04
├─sdb4 vfat 25B3-0EF5 c5c96d4d-c78d-4202-bc95-2d69071db184
└─sdb5 ext4 28fcfd08-e98e-4232-a2ea-9f6a189ede2c abcaa3f5-4dd9-4343-8eed-7deb63896cf4
sdc
└─sdc1 vfat 9C8F-C854 0bef4ffb-01 ESD-USB
nvme0n1
└─nvme0n1p1 ntfs 3F9566522965A5FA 25ba2797-ce2f-49f8-9f7a-dac44f3f886c m2drive
df (filtered): _________________________________________________________________
Avail Use% Mounted on
nvme0n1p1 931.4G 0% /mnt/boot-sav/nvme0n1p1
sda1 69.5M 28% /mnt/boot-sav/sda1
sda3 430G 8% /mnt/boot-sav/sda3
sda4 88.1M 83% /mnt/boot-sav/sda4
sdb2 444.4G 68% /media/mom/SSD
sdb4 512M 0% /mnt/boot-sav/sdb4
sdb5 399.8G 6% /
sdc1 27.7G 13% /mnt/boot-sav/sdc1
Mount options: __________________________________________________________________
nvme0n1p1 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sda3 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sda4 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sdb2 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
sdb4 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sdb5 rw,relatime,errors=remount-ro
sdc1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
====================== sdb5/boot/grub/grub.cfg (filtered) ======================
Ubuntu 28fcfd08-e98e-4232-a2ea-9f6a189ede2c
Ubuntu, with Linux 5.11.0-38-generic 28fcfd08-e98e-4232-a2ea-9f6a189ede2c
Ubuntu, with Linux 5.11.0-37-generic 28fcfd08-e98e-4232-a2ea-9f6a189ede2c
Windows 10 (on sda1) E6AEBF89FEEF81E1
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###
========================== sdb5/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb5 during installation
UUID=28fcfd08-e98e-4232-a2ea-9f6a189ede2c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb4 during installation
/swapfile none swap sw 0 0
======================= sdb5/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=
lsb_release -i -s 2> /dev/null || echo DebianGRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
==================== sdb5: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
1617.310562134 = 1736.573992960 boot/grub/grub.cfg 2
1815.045536041 = 1948.890304512 boot/grub/i386-pc/core.img 1
1425.402019501 = 1530.513764352 boot/vmlinuz 1
1415.183261871 = 1519.541456896 boot/vmlinuz-5.11.0-37-generic 1
1425.402019501 = 1530.513764352 boot/vmlinuz-5.11.0-38-generic 1
1415.183261871 = 1519.541456896 boot/vmlinuz.old 1
1427.652915955 = 1532.930646016 boot/initrd.img 2
1423.705074310 = 1528.691683328 boot/initrd.img-5.11.0-37-generic 3
1427.652915955 = 1532.930646016 boot/initrd.img-5.11.0-38-generic 2
1423.705074310 = 1528.691683328 boot/initrd.img.old 3
===================== sdb5: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 18151 Aug 12 04:18 10_linux
-rwxr-xr-x 1 root root 42359 Aug 12 04:18 10_linux_zfs
-rwxr-xr-x 1 root root 12894 Aug 12 04:18 20_linux_xen
-rwxr-xr-x 1 root root 12059 Aug 12 04:18 30_os-prober
-rwxr-xr-x 1 root root 1424 Aug 12 04:18 30_uefi-firmware
-rwxr-xr-x 1 root root 214 Aug 12 04:18 40_custom
-rwxr-xr-x 1 root root 216 Aug 12 04:18 41_custom
======================== Unknown MBRs/Boot Sectors/etc =========================
/dev/sda1: unknown GPT attributes
8000000000000000
/dev/sda2: unknown GPT attributes
8000000000000000
/dev/sda4: unknown GPT attributes
8000000000000001
Unknown BootLoader on nvme0n1p1
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|
00000010 00 00 00 00 00 f8 00 00 20 00 40 00 00 08 00 00 |........ .@.....|
00000020 00 00 00 00 80 00 80 00 ff 5f 70 74 00 00 00 00 |........._pt....|
00000030 04 00 00 00 00 00 00 00 ff 05 47 07 00 00 00 00 |..........G.....|
00000040 f6 00 00 00 01 00 00 00 fa a5 65 29 52 66 95 3f |..........e)Rf.?|
00000050 00 00 00 00 0e 1f be 71 7c ac 22 c0 74 0b 56 b4 |.......q|.".t.V.|
00000060 0e bb 07 00 cd 10 5e eb f0 32 e4 cd 16 cd 19 eb |......^..2......|
00000070 fe 54 68 69 73 20 69 73 20 6e 6f 74 20 61 20 62 |.This is not a b|
00000080 6f 6f 74 61 62 6c 65 20 64 69 73 6b 2e 20 50 6c |ootable disk. Pl|
00000090 65 61 73 65 20 69 6e 73 65 72 74 20 61 20 62 6f |ease insert a bo|
000000a0 6f 74 61 62 6c 65 20 66 6c 6f 70 70 79 20 61 6e |otable floppy an|
000000b0 64 0d 0a 70 72 65 73 73 20 61 6e 79 20 6b 65 79 |d..press any key|
000000c0 20 74 6f 20 74 72 79 20 61 67 61 69 6e 20 2e 2e | to try again ..|
000000d0 2e 20 0d 0a 00 00 00 00 00 00 00 00 00 00 00 00 |. ..............|
000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would purge (in order to fix packages) and reinstall the grub-efi-amd64-signed of
sdb5,
using the following options: sda1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file
Blockers in case of suggested repair: __________________________________________
WindowsEFI detected. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode.
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the The OS now in use - Ubuntu 20.04.3 LTS CurrentSession entry (sda1/efi/****/shim****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\shim****.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.
-
Anonymous
2021-10-15T17:07:42+00:00 Yes.. I just did the sysprep on the other computer. Put back in broken computer and it's still sitting on the window block screen..and yes on the other computer. I only had the SSD drive I was wanting windows on plugged in...
-
Anonymous
2021-10-15T16:50:45+00:00 Linux tells us that the problem is almost certainly with WIndows.
On the drive you are transferring Windows after install on the other PC, can you put it back in the other PC and Sysprep it to remove drivers and SID so that it is adjusted to start on any hardware?
Did you use this same media to install in the other PC, booting it to do a Custom Install? That confirms the media is good. Did you unplug the other internal hard drives? If not the boot files were probably derailed to another hard drive.
-
Anonymous
2021-10-15T16:41:55+00:00 No sir. I can't get into anything windows. I've reset bios numerous times. Taken battery out....did the jumper thing. Could it be GPU? the memory is fine. On Linux the Gpu has worked fine..ugh