Shows this error when installing the cab file using DISM. What to do to rectify? Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f081f PS: I am running beta 22621.160. Is that could be the problem?
Reason: https://forums.mydigitallife.net/th...channel-ni_release.85327/page-58#post-1743387 Solution: create uptodate ISO and inplace/repair upgrade. And don't cleanup anymore afterwards.
Updated successfuly .160 -> .169 in non supported hardware. for those who think uupdump created isos are causing troubles, it is not. Code: Running W10UI v10.18 ============================================================ ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/2: Windows11.0-KB5014958-x64.cab [LCU] 2/2: Windows11.0-KB5015713-x64.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.1 Image Version: 10.0.22621.160 Processing 1 of 1 - Adding package Package_for_ServicingStack_169~31bf3856ad364e35~amd64~~22621.169.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_169 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.1 Image Version: 10.0.22621.160 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5 [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ ============================================================ System restart is required to complete installation ============================================================ Press 9 to exit.
Windows runs cleanups itself frequently. As soon as my second pc is online again i can check, it runs 22621.160.0.3 atm but atm i have a pc from a client to fix so i had to make room for it on my desk.
When i ran "sfc /scannow" got some corrupt files but it didn't help. After restart got the same error. Code: Microsoft Windows [Version 10.0.22621.160] (c) Microsoft Corporation. Wszelkie prawa zastrzeżone. C:\dism.exe /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.22621.1 Image Version: 10.0.22621.160 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. C:\dism.exe /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.22621.1 Image Version: 10.0.22621.160 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. C:\sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag. Code: ============================================================ Running W10UI v10.18 ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/1: Windows11.0-KB5014958-x64.cab [LCU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.1 Image Version: 10.0.22621.160 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f081f Error: 0x800f081f DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press 9 to exit
links under account protection in windows defender dont take you to the correct page, view your account info Manage sync settings manage sign in options dynamic lock settings Have no idea if this a recent bug as ive never tried these links
You can run disk cleanup? it doesnt tamper with system files, only removes redundant upgrade packages?
My path: 1) did an upgrade install from the official 22621.1 ISO image 2) used W10UI to upgrade to 22621.160 3) signed up for Windows Insider Release Preview 4) Windows update offered 22621.169 and it installed successfully The above steps were spread out over a period of weeks. I just used Vivetool to enable tabs on Windows File Explorer, it's about time Microsoft added that option!
10 21H2 upgraded to 25151 via WU, restored back to 10, then upgraded again to 22621.160 via WU, enrolled to RP and installed .169 just fine. unsupported machine
https://forums.mydigitallife.net/posts/1712330/ https://forums.mydigitallife.net/posts/1735960/ Always try to use the msu (original or repacked)