@ultimate_live 19042/19043/19044 are fake builds, they are all 19041 build + updates and enablement package
Today I downloaded this Build 19043.1149, and after install it shows v2004 Build 19041.1. Shouldn´t it be 21H1 Build 19043.1149?
Hi. I don´t know, why it shows errors now. Download was completed without erors but now while creting, it show errors. Here are some of them. Code: ============================================================ Running UUP -> ISO v67 ============================================================ ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Configured Options . . . ============================================================ AutoStart 1 AddUpdates 1 Cleanup NetFx3 StartVirtual ============================================================ Preparing Reference ESDs . . . ============================================================ CAB->ESD: microsoft-onecore-applicationmodel-sync-desktop-fod-package-amd64 CAB->ESD: microsoft-onecore-directx-database-fod-package-amd64 CAB->ESD: microsoft-windows-hello-face-migration-package-amd64 CAB->ESD: microsoft-windows-hello-face-package-amd64 CAB->ESD: microsoft-windows-internetexplorer-optional-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-basic-de-de-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-handwriting-de-de-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-ocr-de-de-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-speech-de-de-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-texttospeech-de-de-package-amd64 CAB->ESD: microsoft-windows-mediaplayer-package-amd64 CAB->ESD: microsoft-windows-mspaint-fod-package-amd64 CAB->ESD: microsoft-windows-notepad-fod-package-amd64 CAB->ESD: microsoft-windows-powershell-ise-fod-package-amd64 CAB->ESD: microsoft-windows-printing-pmcppc-fod-package-amd64 CAB->ESD: microsoft-windows-printing-wfs-fod-package-amd64 CAB->ESD: microsoft-windows-quickassist-package-amd64 CAB->ESD: microsoft-windows-stepsrecorder-package-amd64 CAB->ESD: microsoft-windows-tabletpcmath-package-amd64 CAB->ESD: microsoft-windows-userexperience-desktop-package-amd64 CAB->ESD: microsoft-windows-wordpad-fod-package-amd64 CAB->ESD: openssh-client-package-amd64 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 8 threads Archiving file data: 7254 MiB of 7254 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 201 MiB of 201 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 249 MiB of 249 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 227 MiB of 227 MiB (100%) done ============================================================ Updating install.wim / 4 image(s) . . . ============================================================ 1/6: ssu-19041.1145-x64.cab [SSU] 2/6: windows10.0-kb5000736-x64.cab [Enablement] 3/6: windows10.0-kb5000983-x64.cab [WinPE] 4/6: windows10.0-kb5001679-x64.cab 5/6: windows10.0-kb5004296-x64.cab [LCU] 6/6: windows10.0-kb5004313-x64.cab [Setup DU] Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1145.1.2 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Image Version: 10.0.19041.1 Error: 87 The add-package option is unknown. For more information, refer to the help by running DISM.exe /?. The DISM log file can be found at C:\Windows\Logs\DISM\DismUpdt.log Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Image File : C:\Users\Administrator\Downloads\19043.1149_amd64_de-de_multi_9acda6c6_convert_virtual\ISOFOLDER\sources\install.wim Image Index : 1 Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. The DISM log file can be found at C:\Windows\Logs\DISM\DismNetFx3.log Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. The DISM log file can be found at C:\Windows\Logs\DISM\DismNetFx3.log Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Error: 50 The request is not supported. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Error: 50 The request is not supported. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1145.1.2 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.14393.4169 Image Version: 10.0.19041.1 Error: 87 The add-package option is unknown. For more information, refer to the help by running DISM.exe /?. The DISM log file can be found at C:\Windows\Logs\DISM\DismUpdt.log
He's not the only one. I saw this as well and there was at least 1 other in that other thread. It looked like the CU got integrated but the EP didn't.
Can you provide this log zipped as attachment, for @abbodi1406 to review? And can you set the Convert-UUP.cmd to debug = 1 and re-run the cmd? Line 45 Code: :: change to 1 to enable debug mode set _Debug=1
I also had the issue on Windows 8.1 probably caused by ssu-19041.1145 (not compatible for offline servcing on OS below 19041)
abbodi1406. Checked here. Windows Server 2016 v1607 Build 14393.4470 Is there a way to fix it to make dism work again without erros?
I don´t know why it stopped working now, if it was always working fine on Windows Server. Now MSMG Toolkit (dism) isn´t working now. Tried to integrate KB5003537 and didn´t work. Can´t change from Windows Server to Windows 10, because it is a Dedicated server.