Installation of Windows 11 encountered issues, yet standard fixes aren't effective.
Installation of Windows 11 encountered issues, yet standard fixes aren't effective.
I need support from the community since I’m running out of troubleshooting options. First, please accept my apologies for any spelling or grammar mistakes—I’m still learning English. My system is an Intel Core i5-12600K with a Gigabyte Z690 UD AX DDR5 motherboard, 2 x 16 GB ADATA XPG 5200 MHz RAM, Sapphire Nitro RX 6600XT graphics card. The problem is happening with all drives I’ve tested: NVMe SSDs, SATA SSDs, and a hard drive. Unfortunately, my Windows 11 PC got infected by malware, so I had to reset it. The standard Windows reset didn’t work, so I used GParted to wipe everything clean before the infection. Before that, I faced several Blue Screens, which I accepted due to lack of solutions. The main error message was “Attempt to write to read-only memory.” Now I’m attempting a clean installation of Windows, but it keeps failing at 22% or 23% with the warning “Windows 11 Installation has failed.”
What I’ve tried so far:
- Installed Windows via ISO and USB using Media Creation Tool; it worked on other systems.
- Tried Ubuntu without issues.
- Used integrated GPU and removed extra devices.
- Installed on multiple NVMe SSDs, one HDD, and one SATA SSD (configured with Diskpart and GParted).
- Updated BIOS settings.
- Checked all available Windows versions through the Media Creation Tool.
I suspect a possible driver issue on the motherboard, but I’m not sure how to resolve it. Any suggestions would be greatly appreciated—I’d love your help!
Execute MemTest86 using a USB flash drive. Should it detect issues, the Windows setup will also encounter problems. https://www.memtest86.com/
I’ll start with a few simple things that keep popping up for me too often and shouldn’t be ignored:
- Switch to another USB stick. I have several that work just fine otherwise, but they won’t boot into the installer or live OS. Some crash on Windows, some on Linux, and a few on both. No clear reason.
- Use a different USB port, ideally one at the back of the machine, preferably USB 3.
- Re-download the ISO file and burn it onto another USB stick using Rufus, or use Ventoy to write the .iso directly into the drive and try again.
- Turn off Fastboot and possibly Secure Boot in BIOS settings and attempt the installation once more.
These steps usually resolved about 99% of my failed Windows installs. Now let’s explore what you’re experiencing next. When the process stops, do you get any error messages or prompts to review logs? Or does it just report a generic failure without details? Have you tried installing Windows on other devices with the same media to confirm the issue is with the USB? Also, I’ve noticed some advice suggesting checking if your BIOS is set to UEFI mode—how would you verify that on your machine? And there’s a comment I’d like to see for extra assurance.
From a functional PC, obtain the Windows 11 24H2 ISO file. Utilize RUFUS to transfer the ISO onto a USB drive. https://www.microsoft.com/en-us/software.../windows11 https://rufus.ie/en Be sure to verify the integrity of your ISO by checking its hash value before use. Published hashes are available and should align with results from the Get-FileHash command. For instance, the English 64-bit hash B56B911BF18A2CEAEB3904D87E7C770BDF92D3099599D61AC2497B91BF190B11 is provided for reference. This step ensures the file remains unaltered and authentic. If you wish to confirm data consistency, run the same hash calculation in PowerShell and compare it with the published value. Additional guidance on using PowerShell can be found via the official help resources.
Thank you for the suggestion! The test completed successfully with no issues, meaning it works as intended.
Unfortunately, those suggestions didn’t work as expected. I used three different USB sticks and also tried the Rufus method on another system. My BIOS is disabled Fastboot and set to UEFI mode, which is the only setting available. The only clue I have is this error message. Could there be an issue with the drivers or something else? I think it might be related to a problem with the installation point, as it always crashes at the same location.