Problem is probably SupersededActions 1 (DisableResetbase 0) in W10UI. Do you use it? Without not problem.
Yes. I just hope future update(s) install fine. Windows became an Oucherating system, not Operating system...
Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.104 An error occurred trying to open - C:\windows10.0-kb4464455-x64_CU_17763.107.cab Error: 0x8007065e Error: 1630 Data of this type is not supported. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
One question...cuz little confused If i'm clean install Windows 10 LTSC 2019 and updated to 17763.55 via Windows Update and where do i go to get 17763.107? N.B: Non Insider
I'm unable to integrate (using w10ui 5.3) either dynamic or full CU into 104 install.wim Spoiler: W10UI ============================================================ Running W10UI v5.3 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/1: Windows10.0-KB4466596-x64.cab ============================================================ Mounting install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ All applicable updates are detected as installed ============================================================ Unmounting install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image File : C:\1809\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding install.wim ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press any key to exit. Spoiler: 104 C:\887\Bin\x64>wimlib-imagex.exe dir c:\1809\install.wim 1 --path=Windows\Winsxs\Manifests | find /i "microsoft-windows-coreos-revision" \Windows\WinSxS\Manifests\amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.104_none_5373e30595892fcb.manifest \Windows\WinSxS\Manifests\amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.1_none_cf47046e682833fd.manifest \Windows\WinSxS\Manifests\amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.55_none_6bd9884532bfc46c.manifest \Windows\WinSxS\Manifests\wow64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.104_none_5dc88d57c9e9f1c6.manifest \Windows\WinSxS\Manifests\wow64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.1_none_d99baec09c88f5f8.manifest \Windows\WinSxS\Manifests\wow64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.55_none_762e329767208667.manifest
Yes of corse. But good idea, maybe I install it one more time. Who knows? maybe it fix the issue. Edit: tried, no help. Probably have to do an in-place upgrade sometime later.
if you do a clean install of win10, you will logically get the last update installed through windows update. if not, you can always install it manually through command prompt.
Unless you are an Insider on the Slow Ring or Release Preview Ring, you will not get 17763.107 on Windows Update. You need to download the.CAB File and manually install it using DISM with CMD w Admin.
Already applied Windows10.0-KB4464455-x64 installing via Windows 10 Updates Installer abbodi1406 and i got 17763.104 now. Which update file should I take to get 17763.107? do need SSU?
To get 17763.107 you need KB4464455 dated 30 October. Same KB number, updated Files. If SSU is already installed no, but SSU gets installed BEFORE CU.