Yes. You are No. 1. Thanks. BTW, look: https://forums.mydigitallife.net/th...lled-in-old-win10-version.82656/#post-1629294 Too bad, I have no that luck: Code: Microsoft Windows [版本 10.0.18363.1171] (c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。 C:\windows\system32>dism /english /image:G: /add-package:z:\ Deployment Image Servicing and Management tool Version: 10.0.18362.1139 Image Version: 10.0.10240.16384 Processing 1 of 2 - Adding package Package_for_KB4565911~31bf3856ad364e35~amd64~~10240.18631.1.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18725.1.4 [==========================100.0%==========================] Error: 0x800f0922 Package Package_for_RollupFix may have failed due to pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\windows\Logs\DISM\dism.log C:\windows\system32> Let me boot and try again. Too bad, it just keep circling. OK. Apply 10240.16384 Home --> Boot --> Shutdown --> Modify registry --> Install updates --> Modify registry --> Boot Error again Code: C:\windows\system32>dism /english /image:g: /add-package:z: Deployment Image Servicing and Management tool Version: 10.0.18362.1139 Image Version: 10.0.10240.16384 Processing 1 of 2 - Adding package Package_for_KB4565911~31bf3856ad364e35~amd64~~10240.18631.1.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18725.1.4 [==========================100.0%==========================] Error: 0x800f0922 Package Package_for_RollupFix may have failed due to pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\windows\Logs\DISM\dism.log C:\windows\system32> Try Professional with my own old registry way. Same error.
oh i only try it with offline image... I am testing it with online image It is super slow to install updates in virtual machine... I will show more details later Yes, it works with online image
Since 18362, it looks like 7601. This is still my guess It would be great if you can find a way to install the update smoothly without modifying the update package master xinso
see. that's why dism++ is dangerous. it's not really fully compatible with dism, does some hacking behind
Compare offline 10240.16384 image + Registry trick + official SSU KB4565911 + official LCU KB4580327 + dism = Failed + dism++ = OK Code: Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18725.1.4 State : Install Pending + pkgmgr = both SSU and LCU installed, but dism /image:G: /get-packages shows only SSU = Failed. Code: C:\windows\system32>dism /image:z:\1 /get-packages 部署映像服務與管理工具 版本: 10.0.18362.1139 映像版本: 10.0.10240.18631 封裝清單: 封裝識別 : Package_for_KB4565911~31bf3856ad364e35~amd64~~10240.18631.1.1 狀態 : 已安裝 版次類型 : Security Update 安裝時間 : 2020/11/10 下午 02:33 操作順利完成。 C:\windows\system32> How about offline 10240.16384 image + my SSU KB4565911 + my LCU KB4580327 + dism = Failed + dism++ = OK Code: Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.18725.1.4 State : Install Pending + pkgmgr = Bypassed
Exactly what I'm using, VBox 5.2.45 (no longer for download) and VirtIO drivers. Unfortunately, all VBox 6.x run like sh*t for me and 6.1 lacks 3D for older OS.
xinso would be a better teacher, if only he would teach, by showing or explaining how to do things, so you could do it for yourself. Last edited: added correct sentence structure