If that is indeed the case, curious to know why (having retrieved the links via UUPDump or Adguard) I can then download the files, but... unable to retrieve the list (accessing the same delivery source) when using the APP... WU REQUEST DENIED
I'm trying to download build 19045.3754, but errors 0xc1420117 always occur when the iso is being created. I have repeated the process several times and this error always occurs. log: Spoiler ============================================================ Running UUP -> ISO v96 ============================================================ ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Configured Options . . . ============================================================ AutoStart 1 AddUpdates 1 SkipWinRE SkipEdge 1 ============================================================ Preparing Reference ESDs . . . ============================================================ Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package-amd64 Microsoft-OneCore-DirectX-Database-FOD-Package-amd64 Microsoft-Windows-Hello-Face-Migration-Package-amd64 Microsoft-Windows-Hello-Face-Package-amd64 Microsoft-Windows-InternetExplorer-Optional-Package-amd64 Microsoft-Windows-LanguageFeatures-Basic-en-us-Package-amd64 Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package-amd64 Microsoft-Windows-LanguageFeatures-OCR-en-us-Package-amd64 Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-amd64 Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package-amd64 Microsoft-Windows-MediaPlayer-Package-amd64 Microsoft-Windows-MSPaint-FoD-Package-amd64 Microsoft-Windows-Notepad-FoD-Package-amd64 Microsoft-Windows-PowerShell-ISE-FOD-Package-amd64 Microsoft-Windows-Printing-PMCPPC-FoD-Package-amd64 Microsoft-Windows-Printing-WFS-FoD-Package-amd64 Microsoft-Windows-QuickAssist-Package-amd64 Microsoft-Windows-StepsRecorder-Package-amd64 Microsoft-Windows-TabletPCMath-Package-amd64 Microsoft-Windows-UserExperience-Desktop-Package-amd64 Microsoft-Windows-WordPad-FoD-Package-amd64 OpenSSH-Client-Package-amd64 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 12 threads Archiving file data: 7249 MiB of 7249 MiB (100%) done ============================================================ Updating install.wim / 1 image(s) . . . ============================================================ 1/5: SSU-19041.3745-x64.cab [SSU] 2/5: Windows10.0-KB5015684-x64.cab [Enablement] 3/5: windows10.0-kb5031474-x64.cab [SafeOS DU] 4/5: Windows10.0-KB5032278-x64.cab [LCU] 5/5: windows10.0-kb5032906-x64.cab [Setup DU] Deployment Image Servicing and Management tool Version: 10.0.19041.844 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3745~31bf3856ad364e35~amd64~~19041.3745.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. Processing 1 of 1 - Staging Windows10.0-KB5032278-x64 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3754.1.18 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image File : C:\w10\ISOFOLDER\sources\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] Error: 0xc1420117 The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image File : C:\w10\ISOFOLDER\sources\install.wim Image Index : 1 Unmounting image [==========================100.0%==========================] Error: 0xc1420117 The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log "ISOFOLDER\sources\install.wim" original size: 5143793 KiB Using LZX compression with 12 threads Archiving file data: 11 GiB of 11 GiB (100%) done "ISOFOLDER\sources\install.wim" optimized size: 5101730 KiB Space saved: 42062 KiB ============================================================ Adding setup dynamic update(s) . . . ============================================================ windows10.0-kb5032906-x64.cab ============================================================ Creating winre.wim . . . ============================================================ Using LZX compression with 12 threads Archiving file data: 971 MiB of 971 MiB (100%) done ============================================================ Updating winre.wim / 1 image(s) . . . ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3745~31bf3856ad364e35~amd64~~19041.3745.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3754.1.18 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.3754 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.3754 [===========================48.7% ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image File : C:\w10\temp\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] Error: 0xc1420117 The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image File : C:\w10\temp\winre.wim Image Index : 1 Unmounting image [==========================100.0%==========================] Error: 0xc1420117 The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log "temp\winre.wim" original size: 719770 KiB Using LZX compression with 12 threads Archiving file data: 1056 MiB of 1056 MiB (100%) done "temp\winre.wim" optimized size: 446537 KiB Space saved: 273232 KiB ============================================================ Creating boot.wim . . . ============================================================ ============================================================ Creating ISO . . . ============================================================ OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (500 files in 41 directories) Scanning source tree complete (905 files in 86 directories) Computing directory information complete Image file is 5986385920 bytes (before optimization) Writing 905 files in 86 directories to 19045.3754.231110-1737.22H2_RELEASE_SVC_PROD2_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO 100% complete Storage optimization saved 25 files, 14200832 bytes (1% of image) After optimization, image file is 5974237184 bytes Space saved because of embedding, sparseness or optimization = 14200832 Done. Finished. ============================================================ Removing temporary files . . . ============================================================ Press 0 to exit.
Have you tried cleaned up after faild dl In some cases, an image can be corrupted while modifying it with DISM. Use /Cleanup-MountPoints to repair it. This command will not unmount images that are already mounted, nor will it delete images that can be recovered using the /Remount-Image command. Dism /Cleanup-Mountpoints
I think it's just about low disk space p.s. Cleanup-MountPoints is already in the Remove_Failure_MountDir_TempDir.cmd script, just run it
Not sure if this is what you are looking for... Code: gethostbyname 111.221.29.40 [gap-prime-finance.msn-int.com] IP hostname gap-prime-finance.msn-int.com DNS fe3cr.delivery.mp.microsoft.com ping gap-prime-finance.msn-int.com *Note DNS --> fe3cr.delivery.mp.microsoft.com Pinging gap-prime-finance.msn-int.com [111.221.29.40] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 111.221.29.40: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), ping fe3cr.delivery.mp.microsoft.com *Note ---> Different address from one above Pinging glb.cws.prod.dcat.dsp.trafficmanager.net [20.166.126.56] with 32 bytes of data: Reply from 20.166.126.56: bytes=32 time=12ms TTL=114 Reply from 20.166.126.56: bytes=32 time=12ms TTL=114 Reply from 20.166.126.56: bytes=32 time=12ms TTL=114 Reply from 20.166.126.56: bytes=32 time=11ms TTL=114 Ping statistics for 20.166.126.56: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 12ms, Average = 11ms
I'm just thinking that if your router itself cannot communicate with those servers, then you are 1.) ruling out your PC and 2.) confirming if your ISP is blocking access.
I have 2 seperate routers ( 2 completely different ISP Providers), So Router ? unlikely... 1 ISP blocking access, maybe... but both??? also ... don't have any issue (with the main 3GB service, apart from this one) accessing any web site, and with the second (VM325) service, can access anywhere via the (CyberGhost ) VPN. everything worked up until the upgrade to 25992... cause will probably turn out to be something really silly (egg on face scenario)
How does 1809 install LCU after 2020-11/10 into all SKUs? Shouldn’t the Home & Pro SKU be unable to support it?
Home is removed they could not remove Professional, because it's the CBS edition for Enterprise/Education installing online on Pro itself may fail and revert (supplemental servicing check), but can be installed offline without issue Professional is still not removed from 1809 updates applicability