Expanding Files 0%, error 0x80070017 Windows 7 x64 RTM

0

I have downloaded Windows 7 x64 from MSDN. I have checked the hash of the file and it is correct. I have them made a bootble USB stick (http://kmwoley.com/blog/?p=345 (had to use my vista bootsect.exe as running 32bit at the moment). When I boot from the USB it fails when expanding the file. It stays on 0% and fails after around 90 seconds. The error is 0x80070017. As the hash is correct and I am using USB I guess it could be a hardware problems. Any advice how to get Windows 7 installed? The machine is a Dell Studio Slim.

windows-7
usb
installation
usb-flash-drive
asked on Super User Aug 31, 2009 by (unknown user) • edited Jun 15, 2010 by quack quixote

5 Answers

2

The error code you're seeing is ERROR_CRC:

Data error (cyclic redundancy check)

The usual follow-up would be to verify the contents of the installation media. You've mentioned that the "hash is correct"; did you make sure to re-hash the media after copying it onto your USB key? (It's possible that a few bits got flipped between the downloaded copy and the copy on the key.) Alternatively, do you have another USB key or device that you could try?

answered on Super User Sep 5, 2009 by Reuben
1

try WinToFlash

worked for me with win7x86.

answered on Super User Aug 31, 2009 by (unknown user)
1

You are all wrong ;) except for the use of a bootable USB.

The 0x80070017 means the DVD did not burn correctly, or the ISO image was corrupted.

Make sure the MD5 checksum of your ISO file is: 758887088235024058d1c8eb6efb85a8

3.00 GB (3,224,686,592 bytes)

If they match, try burning that ISO on a different computer with a DVD burner.

I had this same problem and I fixed it.

Also if your do the win7 upgrade from 32 bit to 64 or just a 'clean install' from the 'upgrade' you will need a registry hack.

answered on Super User Jan 15, 2010 by tcables
0

Try formatting the drive. I tried installing on top of a Vista partition and had the same problem. Deleting partition and recreating solved the issue for me.

answered on Super User Sep 1, 2009 by (unknown user)
0

I have had this before and it was down to corrupt memory. Run a memory checker on your machine such as memtest86+

answered on Super User Sep 19, 2009 by William Hilsum

User contributions licensed under CC BY-SA 3.0