Attempt at making Vista Offline Updater Script

Discussion in 'Windows Vista' started by Chuterix, May 22, 2023.

Tags:
  1. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,455
    92,500
    340
    What's wrong with DISM 8.1?
    i can integrate Vista updates sucessfully on Windows 8.1

    dism eventually load built-in Vista pkgmgr regardless
    Code:
    dism /image:"C:\Mount\\" /sysdrivedir:"C:\Mount\\" /quiet /norestart /add-package /packagepath:Windows6.0-KB960362-x86.cab /ignorecheck
    --->
    C:\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe /o:"C:\Mount\;C:\Mount\Windows" /ip /m:"Windows6.0-KB960362-x86.cab" /quiet /norestart /l:"C:\WINDOWS\Logs\DISM\dism.log.pkgmgr" /s:"C:\Users\Abbodi\AppData\Local\Temp\A732AA84-49E6-41E7-B332-0988DA22379F"
     
  2. George King

    George King MDL Expert

    Aug 5, 2009
    1,961
    2,468
    60
    Thats work for you only when you use /sysdrivedir, otherwise it ends in PKGMGR was removed in 8.1 or similar. I don't remember it exactly.

    8.0 is also last fully compatible with XP and Vista, some future updates broke this compatibility in XP. In Vista probably still works latest 8.0 DISM with it's updates (I have not checked depencies yet).

    Another issue I remember was, when I tried service Vista that had different SSU, I won't call build in PKGMGR.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    628
    364
    30
    I'm trying to integrate the updates but it doesn't work, PKGMGR (from DISM 8.0) seems to report no the path is not correct when it really is..

    Code:
    Code:
    "%~dp0apps\waik\x86\DISM\dism.exe" /image:"%IMAGE%" /add-package /packagepath:"%~dp0updates\extracted\Windows6.0-KB4493730-%ARCH%\update.mum" /LogPath:"%~dp0Logs\Update.log"
    Log PKGMGR:
    Code:
    2023-12-16 05:15:44, Info                  CBS    Pkgmgr: called with: "C:\VistaUpdateISO\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\pkgmgr.exe /l:"C:\VistaUpdateISO\Logs\Update.log.pkgmgr" /o:"C:\VistaUpdateISO\Mount;C:\VistaUpdateISO\Mount\Windows" /ip /m:"C:\VistaUpdateISO\updates\extracted\Windows6.0-KB4493730-x64\update.mum" /s:"C:\Users\Yogenis\AppData\Local\Temp\6EDC3CA4-8D26-4D6F-A4B3-3324CDD102FB""
    00000001@2023/12/16:09:15:44.598 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0xfb165f @0xfab8ea @0xfac368 @0x750cfa29 @0x77177a7e)
    2023-12-16 05:15:44, Info                  CSI    00000001@2023/12/16:09:15:44.598 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0xfb165f @0xfab8ea @0xfac368 @0x750cfa29 @0x77177a7e)
    2023-12-16 05:15:44, Info                  CBS    Must be doing offline servicing, using stack version from: C:\VistaUpdateISO\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\cbscore.dll
    2023-12-16 05:15:44, Info                  CBS    Loaded Servicing Stack v6.0.6002.18005 with Core: C:\VistaUpdateISO\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\cbscore.dll
    00000002@2023/12/16:09:15:44.602 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0x6955854e @0x695363a1 @0xfb2aaf @0xfb2bfd @0xfa4803)
    2023-12-16 05:15:44, Info                  CSI    00000002@2023/12/16:09:15:44.602 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0x6955854e @0x695363a1 @0xfb2aaf @0xfb2bfd @0xfa4803)
    00000003@2023/12/16:09:15:44.605 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0x6958e7b6 @0x69570f93 @0xfb2aaf @0xfb2bfd @0xfa4803)
    2023-12-16 05:15:44, Info                  CSI    00000003@2023/12/16:09:15:44.605 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x69618a50 @0x6958e7b6 @0x69570f93 @0xfb2aaf @0xfb2bfd @0xfa4803)
    00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #4# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x8bf1f4->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[118]"\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/VistaUpdateISO/Mount/Windows/System32/config/SYSTEM\Select\"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 9171496 (0x008bf228))
    2023-12-16 05:15:46, Error                 CSI    00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #4# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x8bf1f4->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[118]"\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/VistaUpdateISO/Mount/Windows/System32/config/SYSTEM\Select\"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 9171496 (0x008bf228))[gle=0xd0000034]
    00000005@2023/12/16:09:15:46.331 (F) d:\longhorn\base\wcp\sil\merged\ntu\ntsystem.cpp(3247): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
    2023-12-16 05:15:46, Error                 CSI    00000005@2023/12/16:09:15:46.331 (F) d:\longhorn\base\wcp\sil\merged\ntu\ntsystem.cpp(3247): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
    [gle=0x80004005]
    00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #3# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenRegistryKey(flags = 0, da = (KEY_READ), kn = [ml:238{119},l:236{118}]"\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/VistaUpdateISO/Mount/Windows/System32/config/SYSTEM\Select\", key = NULL, disp = (null))
    2023-12-16 05:15:46, Error                 CSI    00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #3# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenRegistryKey(flags = 0, da = (KEY_READ), kn = [ml:238{119},l:236{118}]"\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/VistaUpdateISO/Mount/Windows/System32/config/SYSTEM\Select\", key = NULL, disp = (null))[gle=0xd0000034]
    2023-12-16 05:15:46, Error                 CBS    Failed to load offline CSI store from boot directory: '\\?\C:\VistaUpdateISO\Mount\' and windows directory: '\\?\C:\VistaUpdateISO\Mount\Windows\' hr =0x80070002
    2023-12-16 05:15:47, Info                  CBS    Pkgmgr: return code: 0x2
    
     
  4. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    133
    51
    10
    @George King
    Hi, I can successfully integrate KB4474419-v4 offline on host OS Windows 8.x (with host OS's DISM)
    But I cannot integrate KB4474419-v4 offline with Windows 8.0 DISM on host OS Windows 10/11

    Here is the log. How can I solve this problem?

    Update.log
    Code:
    2024-06-22 16:19:22, Info                  DISM   DISM.EXE: The target image version is: 6.0.6002.18005.
    2024-06-22 16:19:22, Info                  DISM   DISM.EXE: The target image is downlevel and considered supported. Looking for PkgMgr.exe.
    2024-06-22 16:19:22, Info                  DISM   DISM.EXE: Executing DISM against a downlevel image. Calling D:\Mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\pkgmgr.exe
    2024-06-22 16:19:22, Info                  DISM   DISM Provider Store: PID=26740 TID=29452 Getting Provider Compatibility Manager - CDISMProviderStore::GetProvider
    2024-06-22 16:19:22, Info                  DISM   DISM Provider Store: PID=26740 TID=29452 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2024-06-22 16:19:22, Info                  DISM   Compatibility Manager: PID=26740 TID=29452 Processing the top level command token(add-package). - CCbsCliParser::Private_ValidateCmdLine
    2024-06-22 16:19:22, Info                  DISM   Compatibility Manager: PID=26740 TID=29452 PackageManager command is being executed: D:\Mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\pkgmgr.exe /l:"Logs\Update.log.pkgmgr" /o:"D:\Mount;D:\Mount\Windows" /ip /m:"x64\FILES\Windows6.0-KB4474419-v4-x64\update.mum" /s:"C:\Users\zyn\AppData\Local\Temp\32147229-8957-4C82-BE26-3C7050F937A1" - CCompatManager::InternalExecuteCommand
    2024-06-22 16:19:51, Info                  DISM   Compatibility Manager: PID=26740 TID=29452 PackageManager return code = 0x57 - CCompatManager::InternalExecuteCommand
    2024-06-22 16:19:51, Error                 DISM   Compatibility Manager: PID=26740 TID=29452 base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:971 - CCompatManager::ProcessPackageList(hr:0x80070057)
    2024-06-22 16:19:51, Error                 DISM   Compatibility Manager: PID=26740 TID=29452 base\ntsetup\opktools\dism\providers\compatprovider\dll\compatmanager.cpp:590 - CCompatManager::CompatExecuteCmdLine(hr:0x80070057)
    2024-06-22 16:19:51, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2024-06-22 16:19:51, Info                  DISM   DISM.EXE:
    2024-06-22 16:19:51, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2024-06-22 16:19:51, Info                  DISM   DISM.EXE:
    

    Update.log.pkgmgr.txt
    Code:
    2024-06-22 16:19:50, Info                  CBS    Doqe: Installing driver Update ID: Package_22_for_KB4474419~31bf3856ad364e35~amd64~~6.0.4.0~4474419-77_neutral_LDR
    2024-06-22 16:19:50, Error                 CBS    Doqe: Failed installing Update ID: Package_22_for_KB4474419~31bf3856ad364e35~amd64~~6.0.4.0~4474419-77_neutral_LDR: 0x80070057
    2024-06-22 16:19:50, Error                 CBS    Doqe: Failed processing queue with hr: 0x80070057
    2024-06-22 16:19:50, Error                 CBS    Doqe: Failed while processing non-critical driver operations queue. hr: 0x80070057
    2024-06-22 16:19:50, Info                  CBS    Doqe: Attempting to undo critical driver operations.
    2024-06-22 16:19:50, Info                  CBS    Doqu: Completed undoing queue.
    2024-06-22 16:19:50, Info                  CBS    Doqe: Attempting to undo driver operations.
    2024-06-22 16:19:50, Info                  CBS    Doqu: Completed undoing queue.
    0000065e@2024/6/22:08:19:50.759 CSI Transaction @0x4293900 destroyed
    2024-06-22 16:19:50, Info                  CSI    0000065e@2024/6/22:08:19:50.759 CSI Transaction @0x4293900 destroyed
    2024-06-22 16:19:50, Info                  CBS    WER: Generating failure report for package: Package_for_KB4474419~31bf3856ad364e35~amd64~~6.0.4.0, status: 0x80070057, failure source: Execute, start state: 0, target state: 7
    2024-06-22 16:19:51, Info                  CBS    Exec: Processing complete.  Session: 31376:464949687, Package: Package_for_KB4474419~31bf3856ad364e35~amd64~~6.0.4.0, hr: 0x80070057
    2024-06-22 16:19:51, Error                 CBS    Pkgmgr: Failed install of package from: D:\NT60\x64\FILES\Windows6.0-KB4474419-v4-x64\update.mum, hr: 0x80070057
    2024-06-22 16:19:51, Info                  CBS    Restored system sleep block state: 0x80000000
    2024-06-22 16:19:51, Info                  CBS    Session: 31376:464949687 finalized.  Reboot required: no
    2024-06-22 16:19:51, Info                  CBS    Pkgmgr: return code: 0x57
    
     
  5. ohault

    ohault MDL Member

    Dec 27, 2022
    227
    71
    10
    What is the latest version of WinsxsLite ?