Problems with 20H2 MCT

Topic

New Reply

I used a formatted 16 GB USB (formatted to Fat32) to download the MCT for the current 20H2 and it goes all the way through the download and then starts to create the files for the USB and goes to the end of the process but throws an error at the end saying that there was an unknown error.

I then did the process all over again and got the same error but this time I got a windows box asking if I want to repair the USB, so I clicked to repair. The process ran and it said that there were no errors found. I then ran dism /Get-WimInfo /WimFile:F:\sources\install.esd /index:1 in a cmd prompt as administrator and it said error with a path to the log file which I looked at but cannot decipher what went wrong.

I looked at the files on the USB and they all seem to be there but am unsure if I should try running them. I’ve never had a problem using the MCT before so I’m a bit alarmed at why I’m now having a problem.

Any help is appreciated.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

1 user thanked author for this post.

Fred

Reply | Quote

Replies

Just to add, I tried the same USB stick on another computer I have and got the same thing. The MCT error and the notification from windows to repair the USB stick which it found no problems with. Maybe there is something that has gone wrong with the USB stick even though windows can’t find anything wrong?

MCT error:

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

1 user thanked author for this post.

Fred

Reply | Quote

CADesertRat wrote:

I used a formatted 16 GB USB (formatted to Fat32)

Format to NTFS (Fat32 is obsolete).
Max file size for Fat32 is 4GB. Windows 10 ISO is ~4.6GB

3 users thanked author for this post.

CADesertRat, Cybertooth, Coldheart9020

Reply | Quote

Alex5723 wrote:

Max file size for Fat32 is 4GB. Windows 10 ISO is ~4.6GB

Max file size for a single file is 4GB.  MCT, targeting a thumb drive, does not copy the ISO, it copies the folders/files contained in the ISO, none of which are larger than 4GB.

The drive size limit for FAT32 is 2TB.

Install.esd is 3.92879GB, fitting nicely within that 4GB file-size limit.

See also #2358548.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

CADesertRat

Reply | Quote

exFAT is the format of choice for USB drives these days.

cheers, Paul

1 user thanked author for this post.

CADesertRat

Reply | Quote

Paul,

Are you saying that I need to format it to exfat instead of ntfs?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Paul T wrote:

exFAT is the format of choice for USB drives these days.

Not for Microsoft’s Media Creation Tool.  The MCT will first format the USB drive FAT32 and then copy the files to it.

I just did it yesterday.

That’s what it looks like in Disk Management.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

CADesertRat

Reply | Quote

[CADesertRat]

So if that’s the case, then my USB stick is bad? I just did a full format to NTFS on it but if it needs to be Fat32 then that indicates that there is a problem with the drive.

This is what it shows in Disk Management now:

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

• This reply was modified 4 years ago by CADesertRat.
• This reply was modified 4 years ago by CADesertRat.

Reply | Quote

CADesertRat wrote:

So if that’s the case, then my USB stick is bad?

That is a possibility.  You could try plugging it in, then go to Administrative Tools > Defragment and Optimize Drives and see if it can be optimized.

Again, when the MCT formats a USB thumb drive, it formats it in FAT32, not NTFS.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

CADesertRat

Reply | Quote

Although Windows probably did a chkdsk  /F operation on your USB stick when it tried to fix it and found no problems, try running “chkdsk  /R” on it and be patient. The /R switch implies /F, but it goes further in its’ examination of the drive’s file structure in that it will also force chkdsk to look for bad sectors in addition to the routines specified by the /F switch.

The one time I ran it on a 500 gig spinner (5400 rpm SATA 3), it took about two hours, so that’s why I said to be patient. Hopefully the check on your 16 gig stick will only take a half hour at the most The /R switch will have chkdsk run 5 separate stages from what I remember, whereas the /F switch only has chkdsk run only 3.

If the /R switch doesn’t find anything, then maybe there is indeed something wrong with the electronics inside the stick, so it would be time to visit your favorite source of supply for a new stick. Luckily 16 gig sticks don’t co$t too much these days. 

BTW, I take it you have your own good reasons for not just using WU to make the jump from 1909 to 20H2?

1 user thanked author for this post.

CADesertRat

Reply | Quote

For what it’s worth, whenever one plugs a USB thumb drive into a Windows PC, right-clicks on the drive and selects “Format”, Windows pops up this dialog box:

The Windows default format (I’m on 20H2 OS Build 19042.928) for a USB thumb drive is still FAT32.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

CADesertRat

Reply | Quote

Thanks bbearren,

I just ran the MCT after doing a full format to NTFS and evidently it worked. It formatted it as Fat 32 in the process.

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Details for image : F:sourcesinstall.esd

Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 15,489,142,996 bytes
WIM Bootable : No
Architecture : x64
Hal : acpiapic
Version : 10.0.19041
ServicePack Build : 631
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 23928
Files : 95308
Created : 11/18/2020 – 8:01:05 PM
Modified : 4/18/2021 – 8:55:36 AM
Languages :
en-US (Default)

The operation completed successfully.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Looking at the version and bld #, it looks like I got 2004 19041.631 instead of 20H2? I already have 2004 19041.804 right now.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

CADesertRat, you might want to read these two posts on this previous subject:
#2351105 and #2351058

Windows - commercial by definition and now function...

1 user thanked author for this post.

CADesertRat

Reply | Quote

Microfix,

Thanks for the references. I saw PK’s response and I tried Abode’s cmd but it didn’t return anything.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

After reading some more on those links, if I understand correctly, by installing the older version of 2004 you then have to run WU to get 20H2? Then run WU to get current on 20H2? Sorry to be so dense, just trying to figure out the process.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

If you just downloaded the MCT and made an ISO with it, you have a 20H2 ISO. 2004 is no longer available using the MCT (since 20H2 was released).

Let me explain one more time. 2004 and 20H2 have the same base image based on 2004 (Build 19041). The difference between the two is in 20H2 (19042), the Feature Experience Pack is turned ON. But the base image of both 2004 and 20H2 is the same. That is why you see 19041 using DISM.

It will be the same when 21H1 comes out, b/c it will also have the same base image with 2004 as the core. Let me guess, it will be 19043???

1 user thanked author for this post.

CADesertRat

Reply | Quote

Thanks PK,

So I should show 19042.631 after installing the ISO from the USB and then I would need to get updated past the 631 build. This has gotten so dang confusing anymore when it used to be simple LOL.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

That’s correct. The ISO is only up to date to the time it was created (Oct or Nov 2020, I believe). They don’t make a new ISO but every now and then.

However, if you are connected to the Internet when you upgrade, it will ask you if you want it to look on the Internet for updates during that installation. That is where you need to be careful. If you are using an ISO of the current version (now 20H2), it will update you to 20H2 April updates (current Build).

BUT, if the ISO you are using is actually 2004, watch out, because it will also update you to 20H2 April updates (current Build) if you are online. That is the reason we encourage people to do upgrades OFFLINE, so they can set/change the update settings to get the version and Build they want before connecting. In the case of using a 2004 ISO and wanting to keep 2004, TRV should be set to 2004 before going online to be sure that version is retained.

If you trust MS to do what YOU want, instead of what they want, you may be disappointed.

Be sure to label that USB as 20H2 Build 19042.631 b/c down the road you won’t be able to tell what you have. The proof is in the installation.

1 user thanked author for this post.

CADesertRat

Reply | Quote

[EP]

Paul T wrote:

exFAT is the format of choice for USB drives these days.

cheers, Paul

exFAT is okay for “high capacity” [HC] or “extended capacity” [XC] sized USB flash drives (ex. 32Gb, 64Gb or greater), Paul T

I would NOT use exFAT as the format if the USB drive is less than 32 gigs (ex. 16Gb) – not worth using on relatively small sized usb drives.

• This reply was modified 4 years ago by EP.

Reply | Quote

EP wrote:

not worth using on relatively small sized usb drives.

Because?

cheers, Paul

Reply | Quote