Member Avatar for commando1200

So I have an ISO of Windows 10 x64 and I'm attempting to install it on a brand new hard drive. I start by using PowerISO to mount the image to a virtual drive then install it onto VirtualBox using my product key and all is fine so I start the burn. I was told to burn at slowest possible speed so I did, Attached the new hard drive inserted the DVD-R windows 10 install pops up like normal and I start the install, after 9% into "extracting files" it stops and shuts off and I must restart the whole install again. I have tried with several DVDs but after using 4 and getting to the exact same point of 9% I think it might either be my PowerISO software or my actual burner. Any thoughts, fixes, or suggestions? Thanks.

  • 3 Contributors
  • 2 Replies
  • 262 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by rubberman

Dani AI

Generated

This thread describes a classic installer hang: Windows setup reaching ~9% while "extracting files" almost always points to read/verification errors (bad media, a corrupted ISO, or a flaky optical drive) rather than a Windows installer quirk. already tried multiple discs and a slow burn, which narrows things down but doesn't eliminate media, burner firmware, or image-corruption as likely culprits. ’s suggestion to use the ISO directly is useful for isolating the problem; if the ISO installs fine from a mounted image or a VM, the problem is the physical media/path. ’s BIOS-write theory is unlikely to explain a repeatable 9% extraction failure—modern installers don’t flash BIOS chips during setup.

Recommended troubleshooting (run these in order):

  • Verify the downloaded ISO with a checksum (SHA1/SHA256) to rule out a corrupted download (certutil -hashfile on Windows or sha256sum on Linux).
  • Create a USB installer (Media Creation Tool or Rufus) and attempt installation from USB — this bypasses optical-drive issues entirely.
  • Burn again on different software/hardware with the "verify written data" option enabled, and try a different brand/type of blank (try DVD+R if DVD-R was used).
  • Try the burned disc on another computer to see if the drive is the problem. If the disc fails on multiple machines, the burn or ISO is suspect.
  • If failures persist even from USB, test system RAM (memtest) and try a freshly downloaded ISO; bad RAM can produce extraction errors.

If a VM install is being used only to test the ISO, that’s useful, but for a physical machine install prefer USB media and confirm boot mode (UEFI vs Legacy/CSM) matches the target disk partitioning.

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

There are web articles about this but now that 10 is released I'd try it with articles after the release date. Why the DVD at all? Why PowerISO?

notes a method that uses the .ISO file. Try that method.

The brand new HDD would be prepared in the host OS as usual and some have written that dynamically allocated didn't work so use the other option.

Member Avatar for rubberman

Windows systems since version 7 have not played nice with virtual machines, especially VirtualBox. Why? I think it is because they want to write data, such as the system ID, to the system BIOS Flash memory chip, which is not avilable on most virtual machines. This is one of the reasons why I no longer run ANY Microsoft operating systems, even in virtual machines! The last I could run without problems in a Linux VM was XP... :-(

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.