Hello,
I would suggest you to create latest media. Download the Media Creation Tool using this link:
https://go.microsoft.com/fwlink/?LinkId=691209
Hope this helps!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I must be doing something wrong because I always have the update fail with some BS error like this. What are the proper steps to run this tool?
I download the tool to the desktop. I'm on an Admin account. I insert a 16GB thumb drive. I format it. I start the tool. I point it to the thumb drive. During the phase where the files are copied to the USB, I get some stupid error like this:
Why are my steps not good enough? Where is the hole in my logic? Or is this tool just written poorly. I'd like to use stronger language here as I used to have to start it all over again and burn bandwidth trying this failed endeavor over and over.
I've heard people make it work by running the tool FROM the USB. Why would that matter? I've tried to write files to the thumb drive just after the format and before running the tool to make sure I have successful writes. Doesn't help.
As a workaround today, I left the error up for a bit. Tried to access the thumb drive and it said it needed to be formatted AGAIN! So I did. Then I just opened the C:$Windows.~WS\Sources\Windows and copied the files to the drive by hand. Made the dang thing myself! WHO WRITES THIS STUFF??
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hello,
I would suggest you to create latest media. Download the Media Creation Tool using this link:
https://go.microsoft.com/fwlink/?LinkId=691209
Hope this helps!
Mine is fatter than yours (heh-heh)...
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> DISM /Get-WimInfo /WimFile:E:\Sources\Install.esd /Index:1
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Details for image : E:\Sources\Install.esd
Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,229,531,906 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.18362
ServicePack Build : 175
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 19610
Files : 88906
Created : 6/11/2019 - 9:35:39 PM
Modified : 7/9/2019 - 10:05:52 PM
Languages :
en-US (Default)
The operation completed successfully.
PS C:\WINDOWS\system32>
4 of your folders have different dates, doesn't mean much without comparing the folders with the date change.
I bet if I download one today it will be different again...
Here is a different one on a 32GB device with the same dates as the 8BG device..
The used space is different and more than your 16GB device...
Could be the cluster size used for formatting that makes the difference in the space used.
The default cluster size changes with the device capacity.
See the last picture below, it shows exactly the same used space as yours, I just changed the cluster size to prove it.
The bigger the cluster size the more space gets wasted.
Since the default allocation unit size changes with the size of the device, that explains the difference.
Looks like yours was formatted with Unit Size of 8192 bytes.
Everything seems to match for the same build even if they were created at different dates.
Last 2 devices show the same space occupied, they are formatted with Unit Size 8192, one device is 32GB, I just changed the unit size from 16KB to 8192 B, the other is 8GB just changed the format from 4096 to 8192 B Unit size and the numbers match.
Good thinking. I might have thought all that up myself given enough time. OK, it seems ChkDsk reveals cluster size but calls it "allocation unit" - &, right, it is 8192 for mine...
C:\WINDOWS\system32>ChkDsk E:
The type of the file system is FAT32.
Volume ESD-USB1903 created 7/9/2019 10:13 PM
Volume Serial Number is 8E09-EE84
Windows is verifying files and folders...
File and folder verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
15,214,592 KB total disk space.
16 KB in 2 hidden files.
744 KB in 84 folders.
3,999,656 KB in 943 files.
11,214,168 KB are available.
8,192 bytes in each allocation unit.
1,901,824 total allocation units on disk.
1,401,771 allocation units available on disk.
It's a fairly instantaneous ChkDsk. Again, good thinking. I accept the explanation. As for the date differences, my dates seem to match what is in my DISM...
Created : 6/11/2019 - 9:35:39 PM
Modified : 7/9/2019 - 10:05:52 PM
I believe "Created" is the date MSFT made/released the Windows image (if I may call it that) that MediaCreationTool1903.exe (MCT) downloads. And "Modified" is the date I ran MCT to (do the download &) create the Windows Installation media. Turning OFF "Hide protected operating system files" in Folder Options, I see my System Volume Information folder is 7/9/2019, which matches Modified.
I guess you ran MCT on the very day MSFT released 175 which was 6/11/2019. That made all your folder dates to be the same date. Then, on 7/8/2019, you modified the contents of the Sources folder at 7:46 PM. I don't know what to make of your System Volume Information folder which is dated 7/24/2019. I'd rather have seen it be another 7/8/2019.
Edit: Now I see it was another 7/8/2019 in your earlier listing (of the 8 GB Sandisk Cruiser). That makes sense. When you changed the Sources folder, it must have also modified the volume information. But the 32GB device remains a puzzle.