Issue to 2025 ISO file and also setup problem

If those two hashes do not match perfectly, it means your ISO file was corrupted during the download process (usually due to a network glitch or dropped packets). That corrupted file is the exact reason you are getting the 0xc0000098 boot error.

Your next steps:

Delete that bad ISO file immediately so you don't accidentally use it again.

Re-download a fresh copy from MSDN (preferably over a stable, wired connection).

Once the new download finishes, run that exact same Get-FileHash PowerShell command again.

Do not try to make a bootable USB with Rufus until those hashes match perfectly. Once they match, you are good to go, Scott Huang .

Hi Scott Huang,

Here is the exact, modern way to verify your ISO file's integrity:

1. Open PowerShell.

Run the following command (replace the path with the actual location of your downloaded ISO): Get-FileHash -Path "C:\path\to\your\WindowsServer2025.iso" -Algorithm SHA256

Compare the generated hash string with the official SHA256 value from the Microsoft Evaluation Center or your Volume Licensing portal.

If they don't match: Your download was corrupted. You just need to download a fresh ISO.

If they DO match: Your ISO is fine, but the USB creation failed. Use a tool like Rufus to recreate the bootable USB drive, as it handles Windows Server ISOs much better than standard burning tools.

I hope this saves you time chasing down old tools! If this resolves your issue, please click "Accept Answer".

Tracy.

The screenshot shows Windows Boot Manager error 0xc0000098 indicating that the boot files (\windows\system32\boot\winload.exe or the BCD configuration) are missing or corrupted. Recovery must be done from proper Windows Server installation media; if the ISO or the media created from it is damaged, both setup and repair will fail.

Use these steps:

1. Verify the Windows Server 2025 ISO
   • If the ISO was downloaded, check that it is not corrupted by validating its SHA‑1 checksum with the Microsoft File Checksum Integrity Verifier (FCIV) tool, similar to the method used for other Microsoft ISOs:
     • Install FCIV.
     • Run in an elevated Command Prompt:

              fciv.exe <ISO-file-name>.iso -sha1
       

     • Compare the returned SHA‑1 value with the checksum provided on the download page. If it does not match, download the ISO again and discard the old one.
   • If the ISO was burned to DVD, recreate the media using a high‑quality disc and a slower burn speed. A bad burn or low‑quality media can cause missing‑file errors during setup and repair.
2. Prefer USB installation media
   • Instead of DVD, create a bootable USB drive from the verified ISO (for example, using the Windows USB/DVD Download tool or similar). This avoids many read errors that cause messages about missing or corrupt files during installation.
3. Boot from the verified media and run repair
   • Boot the server from the known‑good Windows Server 2025 installation media.
   • Choose the correct language and keyboard settings.
   • Select “Repair your computer” instead of “Install now”.
   • Use the automatic repair options to fix startup problems. These tools rebuild boot files and the BCD store so that winload.exe can be found and loaded.
4. If repair still fails
   • Re‑confirm the ISO integrity and the USB/DVD by testing them on another machine or a virtual machine to ensure they boot and start setup correctly.
   • If the media works elsewhere but the server still cannot boot or install, hardware issues (disk or controller) may be present and should be investigated separately.

These steps address both the ISO/media issues and the boot‑loader error shown in the screenshot so that Windows Server 2025 setup and repair can complete successfully.

References:

• "A media driver your computer needs is missing" or "A required CD/DVD drive device driver is missing" error message when you install Windows
• Common issues and workarounds in Visual Studio setup