PENDING SCCM OSD error, cannot read .SWM file that it split itself

[Deilson Oliveira]

I'm creating a standalone image, and the build is Windows 10 20H2, and I created a completely raw task sequence, just containing the image and the default settings of a task sequence, just to validate if everything is ok with the build, but the " install.wim" is above 4GB, so SCCM automatically splits it into two .SWM files (which by the way it creates with a bizarre giant name, and that bothers me a bit, I could put something like "install000.wim" and install .001.wim" and etc.) After I burn the ISO to a USB using FAT32 and NTFS I've already tested it, and in both cases it generates this error, because it can't read the file that it split itself.

Does anyone know how to get around this?