Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Sergey-Galan

macrumors member
May 31, 2024
87
23
Ukraine, Odesa
Correction. With this message I stop.
IMG_0435.jpg
 

startergo

macrumors 603
Original poster
Sep 20, 2018
5,020
2,282
Windows 7 calls BIOS INT10 even when it is booting from UEFI, no matter what video mode the system supports. Windows 7 works in UEFI mode as long there is INT10 support in the firmware.
  • Windows® 7, Windows Vista® with Service Pack 1 (SP1), Windows Server® 2008 R2 and Windows Server® 2008
    • Support UEFI 2.0 or later on 64-bit systems. They also support BIOS-based PCs, and UEFI-based PCs running in legacy BIOS-compatibility mode.
    • Support on Class 2 systems running in legacy BIOS-compatibility mode by using a CSM, so they can use the legacy BIOS INT10 features.
    • Are not supported on Class 3 systems, because these operating systems assume the presence of legacy BIOS INT10 support in the firmware, which is not available in a Class-3 UEFI implementation.
    • Windows Server® 2008 R2 and Windows Server® 2008 also support EFI 1.10 on Itanium-based systems.
It is tricky to install it in UEFI Mode. Legacy mode though should be fine.
 
Last edited:

freqrider

macrumors regular
Feb 10, 2019
213
74
I have a strange issue with Windows Install I can't figure out.

I have a windows 10 install on an mgr (Legacy) drive I have cloned to a new SSD with Clonezilla, which is bootable just fine. I then shrank and or used an existing exfat partition to install windows 11 on. When Win 11 installs it can reboot to windows 11 but win 10 becomes unbootable! I get BSOD with error that a file has changed and windows can not boot. 0x:00000000000e error, I believe? Something about winload.exe being corrupt or not found? Any suggestions? I have edited BCD to reflect current drives. rebuilt mbr with EasyBCD. Only fix is to reclone Win 10 and delete Win 11 install. Any tips? Thanks!

I also have a legacy Ubuntu install on the disk which seems impervious to my shenanigans! ;)
 

freqrider

macrumors regular
Feb 10, 2019
213
74
Are you installing Windows 11 on a disk where Windows 10 is already installed?
Yes, Win 10 is on a separate partition. Win 11 is being installed on a fresh, exfat partition. Seems like Windows installer is modifying whole disk's bootmgr or MBR? I am able to modify BCD to reflect Win 10, 11 entries. Only Win 10 won't boot. Sometimes Win 11 also. I forget, I have tried so many times with varying results.
 
Last edited:

Sergey-Galan

macrumors member
May 31, 2024
87
23
Ukraine, Odesa
Yes, Win 10 is on a separate partition. Win 11 is being installed on a fresh, exfat partition. Seems like Windows installer is modifying whole disk's bootmgr or MBR? I am able to modify BCD to reflect Win 10, 11 entries. Only Win 10 won't boot. Sometimes Win 11 also. I forget, I have tried so manty times with varying results.
During Windows 11 installation, the system partition is set to active and recording occurs Windows PBR to the block device of the system partition appropriate for the file system.
I think the Windows 10 partition is losing this.
And yet, the Windows Install program, when creating a BCD for Win 11, does not take into account the partition with Win 10, but does not touch the BCD, bootmgr, etc. on this partition.
Most likely the solution to the problem is systems on different disks.
 

CACCIATORE

macrumors newbie
Aug 11, 2024
8
0
日本
I created a Windows 10 version of Windows To Go via a USB 2.5 inch HDD/SSD case,then I put the SDD to the SATA slot, I still works fine~
I tired to boot Windows 10 installer via OCLP and installed the Windows dirctetly, It feels normal in the initial use, but after a few days it starts get stuck at the startup LOGO and does not respond.
 

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
Having an issue booting after installing Windows 11 on my CMP 5,1 OCLP 2.0.2 using "Windows Install" app on a NVMe. Tried it on my Mac Pro 6,1 first and it worked no issues running Sequoia and WIndows 11. It installs fine on the CMP but when I first go to boot into Windows after install I get this message.
 

Attachments

  • Screenshot 2024-10-16 at 2.42.25 PM.png
    Screenshot 2024-10-16 at 2.42.25 PM.png
    225.6 KB · Views: 12

startergo

macrumors 603
Original poster
Sep 20, 2018
5,020
2,282
Having an issue booting after installing Windows 11 on my CMP 5,1 OCLP 2.0.2 using "Windows Install" app on a NVMe. Tried it on my Mac Pro 6,1 first and it worked no issues running Sequoia and WIndows 11. It installs fine on the CMP but when I first go to boot into Windows after install I get this message.
Did you install windows in legacy mode? If you install it in UEFI mode better look for support at the OCLP discord. You can try the blue screen view program in Safe Mode to see the error cause:
 
Last edited:

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
Did you install windows in legacy mode? If you install it in UEFI mode better look for support at the OCLP discord. You can try the blue screen view program in Safe Mode to see the error cause:
Installed in UEFI also had no issue with Rufus installer in UEFI mode been doing that for a while just wanted to try out the Install Windows app. It worked like a charm on my 6,1 in UEFI mode.
 
Last edited:

startergo

macrumors 603
Original poster
Sep 20, 2018
5,020
2,282
It worked like a charm on my 6,1 in UEFI mode.
if you look at the link the guy said that it started doing it all of a sudden without any changes. He found that the error was related to the directX, which led him to believe it was related to the video drivers. After uninstall/reinstall of the drivers through DDU he fixed his BSOD. Depending on the results of the debug file analysis you should take the appropriate action. If the same disk boots on another hardware most likely you have driver issues.
 

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
if you look at the link the guy said that it started doing it all of a sudden without any changes. He found that the error was related to the directX, which led him to believe it was related to the video drivers. After uninstall/reinstall of the drivers through DDU he fixed his BSOD. Depending on the results of the debug file analysis you should take the appropriate action. If the same disk boots on another hardware most likely you have driver issues.
I have a RX580, not sure how I can remove drivers when I can't boot into windows at all. The odd thing is I installed Windows 11 UEFI last week with my Rufus thumb drive on the same NVMe but it is an older W11 build but it works and boots no problem, no driver issue. The install on the 6,1 was separate install using the Windows Install app not the same disk, internal disk and I did have to install video drivers for the D500s after the install AMD R5 not Adrenalin.
 

startergo

macrumors 603
Original poster
Sep 20, 2018
5,020
2,282
how I can remove drivers when I can't boot into windows at all
To boot in Safe Mode after a Blue Screen of Death (BSOD) on Windows, you can:


  1. Restart your computer and immediately press and hold the F8 key


  2. Follow the on-screen instructions to switch to Safe Mode


  3. Alternatively, you can:

    • Select Restart now under Recovery options


    • Select Troubleshoot > Advanced options > Startup Settings > Restart


    • Select 4 or F4 or Fn+F4 to start the PC in Safe Mode

Safe Mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in Safe Mode, then the default settings and basic device drivers aren't causing the issue.
 
  • Like
Reactions: macsoundsolutions

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
Thanks will try this, This was originally was just an exercise to make a video and show how easy installing Windows 11 is with the Install Windows app. But now two days later it ain't so easy. With my Mac Pro 6,1 it just worked on the first try.
 

Sergey-Galan

macrumors member
May 31, 2024
87
23
Ukraine, Odesa
Did you install windows in legacy mode? If you install it in UEFI mode better look for support at the OCLP discord. You can try the blue screen view program in Safe Mode to see the error cause:
After looking at the log, the program installed Windows without errors. And you could think about what you wrote above, but there were no problems with the Rufus installer. This is a mystery to me. There are other people here with Mac Pro 5.1 and had no problems installing.
 

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
After looking at the log, the program installed Windows without errors. And you could think about what you wrote above, but there were no problems with the Rufus installer. This is a mystery to me. There are other people here with Mac Pro 5.1 and had no problems installing.
I just tried the rufus install again and the build is from 2022 UEFI. I am a bit stumped. Windows knows it's me installing it as it says hi Lance... and can ID my computer from past install. The install was really fast on a 2 terabyte NVMe with only opencore installed no Mac OS partition. I will try this again with the app. I just wanted to make sure my Rufus install still worked . It must be something about my 5,1 that keeps blocking the boot after installing with the app, as you say it has no problem with the install. I will try to grab the old build and try it with the app.
 
  • Like
Reactions: Sergey-Galan

macsoundsolutions

macrumors regular
Jan 12, 2010
205
101
After looking at the log, the program installed Windows without errors. And you could think about what you wrote above, but there were no problems with the Rufus installer. This is a mystery to me. There are other people here with Mac Pro 5.1 and had no problems installing.
UPDATE! First off let me say how much I appreciate the work Sergey has done with this app, It is amazing, and I think the issue came down to Microsoft's latest builds clashing with my Mac Pro 5,1 as I tried all kinds of things but always wound up with the same error "Kernel Security Check Failure" when booting into Windows 11 for the first time after the install. Maybe it's just a driver issue of some kind I honestly have know clue. Today I was able to get a Windows 10.iso and it installed extremely fast using the app to my NVMe and then my first boot into Windows 10 had no issues. Windows is a finicky bitch! I also was able to take the NVMe with Windows 11 that I created with the app in the 5,1 and put it in my 2019 Mac Pro and it booted no prob which prooves the 5,1 is the problem, the app was not the issue, it's an issue with my 5,1 and maybe the latest Windows 11 build. I can still install Windows 11 using my 2022 Rufus created thumb drive on the 5,1 and get it up to date.
 
Last edited:
  • Like
Reactions: Sergey-Galan

Macschrauber

macrumors 68030
Dec 27, 2015
2,979
1,487
Germany
maybe the SSD?

 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.