Solved Mediacreationtool gives an error - NTFS reparse-point?

After following this guide, http://www.eightforums.com/windows-8-news/56837-official-microsoft-iso-media-creation-tool.html
I am stuck with a problem.

Trying to download a Windows 8.1.1 ISO from Microsoft with their mediacreationtool.exe. I downloaded the program, and I then run this little program and select
Language (Danish)
Edition (Windows 8.1 Pro)
Architecture (64-bit X64)

Then click NEXT

Here I can select either USB flash drive or ISO file. I select ISO-file and click NEXT

Then I select where it saves the ISO-file.

And then the error come allmost instant.

"Download did not complete successfully"
The download task did not complete.
The file or the folder is not a NTFS reparse-point.

I have tried to save on HDD, on a USB-stick formatted NTFS, formatted FAT32, but the same error shows up.

What can I do about this?


EDIT: I have now tried to make the same again, but in English, so it should not be the danish language that gives the error. In English I also got this error, so I would like to get help to this

Where are you saving the iso file?

Same thing is happening to me..

Ztruker said:

Where are you saving the iso file?

Click to expand...

As I write, I have tried on HDDs, on SSD on USB-sticks (both FAT32 and NTFS)

Is you account an Administrator account or a Standard user account?

Again, where (full path please) are you trying to save the file?
How much free space is available on the hard drive or SSD?

I just tried it and it works fine for me under Windows 8.1 Pro X64 to D:\Temp which is on a partition that has 300+GB of free space on my 2TB drive.

It is an Administrator account.

As you on one of the HDD, D:\temp\windows.iso -- 2.490.345.021.440 bytes free aka 2,26Tbyte free(it is a 4Tbyte HDD, NTFS)
On the SSD C:\temp\windows.iso -- 178.605.821.952 bytes free aka 166Gbyte free (it is a 250Gbyte SSD, NTFS)

G:\windows.iso --- On a complete empty (newformatted) 8Gbyte USB2 Patriot XT pen, have tried FAT32 and NTFS

Are you current on Windows Updates?

Run chkdsk c: \f from a Elevated Command Prompt.
Run DISM and SFC from a Elevated Command Prompt:

Press Window key + X
Select Command Prompt (Admin)
Run the following sequentially:


Run all three. If any errors run them a 2nd time.

Found the error. I am using ImDisk's RAMdisk as a tempdrive (to make writings to my SSD lesser), and Microsoft's program don't like that allthough the ramdisk is formatted with NTFS.
As soon as I put the default values for tempfile-placements back, the error is gone

This is the first program I have tried, that did not work with a RAMdisk as tempfiles.
Thank you all for your time spend on trying to find a solution for me

I know this has been said many times, but stop treating the SSD any differently than a normal HDD. You are not going to wear it out or use up the available write cycles it's capable of.

Last I read SSDs will last longer than HDDs.

My recommendation would be to drop the ramdisk, but it's your call.

Yes, it is my call, and I will continue to use the ramdisk, as the speed-advance is great compared to the SSD:



Try and get these numbers from a SSD or a HDD

NB: In the picture the ramdisk is only at 2Gbyte for testing, normally it is at 8 gbyte

Nice numbers for sure. Maybe I should look at doing this as I have 16GB ram.

You have 2 options with this program. Give a little speed when making the ramdisk dynamic in size (ie you have 16 gbyte ram, set the ramdisk to 12 gbyte in dynamic size, and the ramdisk will ONLY take as much ram as necessary, and it can never be increased above 12gbyte. If there is only 0,3Gbyte data in the ramdisk, then it will only consume 0,3Gbyte ram).
The fastest is to have a stationary ramdisk (that is what the numbers in my pic shows). The catch here is, that if you make a ramdisk at 12 Gbyte, then it takes up 12 Gbyte ram nomatter how little data is actually stored in your ramdisk.

Here is the numbers for a dynamic ramdisk. And these numbers can be raised with faster ram (mine is 1866Mhz CL9).

Intresting, I'll take a look.

Thanks