Windows XP Mode

Viewing 45 reply threads
  • Author
    Posts
    • #49033

      I’m just guessing, but I think maybe the file update.mum inside Windows6.1-KB958559-x64.cab is what’s preventing VPC from installing. The file update.mum appears to have a list of valid OS’s, and I think theoretically if we could inject this into the list, it would see R2 as a valid OS.



      However, I wasn’t able to test this because I don’t know how to modify a .cab file. I tried creating a new one with CabPack 1.4, but dism.exe couldn’t open it. Even if it could open it, it would probably fail because then the hashes in the update.cat would be wrong.

      Is there a way to execute the individual .manifest files? Those appear to tell what folders to put the files into, what components to register, and what keys to add into the registry.

    • #49035

      long years ago i modified cab files after then there was a tool to restore the old has of a file. but i dunno exactly the name of the program :geek:

    • #49036

      @GnatGoSplat wrote:

      However, I wasn’t able to test this because I don’t know how to modify a .cab file.

      Try using “iexpress”.

    • #49037

      @GnatGoSplat wrote:

      Well, I followed your guide,
      extracted .msu file (using 7zip), extracted the “Windows6.1-KB958559-x64.cab” to new folder (using 7zip), updated update.mum (using Notepad2), restored update.mum timestamp (using AttributeMagic) back to last value, generated new SHA1 sum of update.mum (using HashCalc), edited SHA1 sum of update.mum in _manifest_.cix.xml (using Notepad2), made a CAB file of all files from the folder containing update.mum (using IExpress), deleted original Windows6.1-KB958559-x64.cab, renamed new CAB to “Windows6.1-KB958559-x64.cab”, made CAB file (using IExpress) from the whole folder (with updated Windows6.1-KB958559-x64.cab) and then renamed the CAB file to Windows6.1-KB958559-x64.msu
      but I’m still getting that “Unsupported OS” error… 🙁

    • #49038

      Here’s a DISM debug of my modified MSU package.

      2009-11-07 17:10:01, Info                  DISM   DISM.EXE: <
      
      Starting Dism.exe session
      >
      2009-11-07 17:10:01, Info DISM DISM.EXE:
      2009-11-07 17:10:01, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7600, Running architecture=amd64, Number of processors=2
      2009-11-07 17:10:01, Info DISM DISM.EXE: Executing command line: dism /NoRestart /Online /LogLevel:4 /Apply-Unattend:Windows6.1-KB958559-x64.xml
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Getting Provider FolderManager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Loading Provider from location C:WindowsSystem32DismFolderProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Connecting to the provider located at C:WindowsSystem32DismFolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Getting Provider FolderManager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=3652 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Manager: PID=3652 Targeting the DISM provider store at "C:WindowsSystem32Dism" - CDISMManager::CreateImageSessionFromLocation
      2009-11-07 17:10:01, Info DISM DISM Manager: PID=3652 Attempting to load the Dism stack from "C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887AB" - CDISMManager::LoadImageSession
      2009-11-07 17:10:01, Info DISM DISM Manager: PID=3652 Successfully loaded the ImageSession at "C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887AB" - CDISMManager::LoadImageSession
      2009-11-07 17:10:01, Info DISM DISM Image Session: PID=2124 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABOSProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABOSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:01, Info DISM DISM OS Provider: PID=2124 Defaulting SystemPath to C: - CDISMOSServiceManager::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM OS Provider: PID=2124 Defaulting Windows folder to C:Windows - CDISMOSServiceManager::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABLogProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABLogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Getting Provider OSServices - CDISMProviderStore::GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABPEProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Warning DISM DISM Provider Store: PID=2124 Failed to Load the provider: C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABPEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Image Session: PID=2124 Obtained the image's logger instance. Configured the image session to use it. - CDISMImageSession::get_ProviderStore
      2009-11-07 17:10:01, Info DISM DISM Manager: PID=3652 Image session successfully loaded from the temporary location: C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887AB - CDISMManager::CreateImageSession
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Getting Provider OSServices - CDISMProviderStore::GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info CSI 00000001 Shim considered [l:256{128}]"??C:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
      2009-11-07 17:10:01, Info CSI 00000002 Shim considered [l:250{125}]"??C:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_SUCCESS
      2009-11-07 17:10:01, Info DISM DISM.EXE: Target image information: OS Version=6.1.7600.16385, Image architecture=amd64
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - CDISMProviderStore::GetProviderCollection
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! - CDISMProviderStore::GetProviderCollection
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABCbsProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABCbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:01, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:01, Info CSI 00000001 Shim considered [l:256{128}]"??C:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
      2009-11-07 17:10:01, Info CSI 00000002 Shim considered [l:250{125}]"??C:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_SUCCESS
      2009-11-07 17:10:01, Info DISM DISM Package Manager: PID=2124 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
      2009-11-07 17:10:01, Info CSI 00000001 Shim considered [l:256{128}]"??C:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
      2009-11-07 17:10:01, Info CSI 00000002 Shim considered [l:250{125}]"??C:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_SUCCESS
      2009-11-07 17:10:01, Info DISM DISM Package Manager: PID=2124 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%logscbscbs.log - CDISMPackageManager::Initialize
      2009-11-07 17:10:01, Info DISM DISM Package Manager: PID=2124 Calling CoCreateInstance to Create CbsSession - CDISMPackageManager::RefreshInstanceAndLock
      2009-11-07 17:10:02, Info DISM DISM Package Manager: PID=2124 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABMsiProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABMsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABIntlProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABIntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABDmiProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABDmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info CSI 00000001 Shim considered [l:256{128}]"??C:WindowsServicingamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
      2009-11-07 17:10:02, Info CSI 00000002 Shim considered [l:250{125}]"??C:WindowsWinSxSamd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810bpkgmgr.exe" : got STATUS_SUCCESS
      2009-11-07 17:10:02, Info DISM DISM OS Provider: PID=2124 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
      2009-11-07 17:10:02, Info DISM DISM Driver Manager: PID=2124 Further logs for driver related operations can be found in the target operating system at %WINDIR%infsetupapi.offline.log - CDriverManager::Initialize
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABUnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABUnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABSmiProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABSmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Loading Provider from location C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABTransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Connecting to the provider located at C:UsersADMINI~1AppDataLocalTemp86CB21CB-7313-4653-BB3D-2BBC808887ABTransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
      2009-11-07 17:10:02, Info DISM DISM.EXE: OSServices does not support command lines.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
      2009-11-07 17:10:02, Info DISM DISM.EXE: DISM Log Provider does not support command lines.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
      2009-11-07 17:10:02, Info DISM DISM.EXE: SmiManager does not support command lines.
      2009-11-07 17:10:02, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
      2009-11-07 17:10:02, Info DISM DISM Transmog Provider: PID=2124 Current image session is [ONLINE] - CTransmogManager::GetMode
      2009-11-07 17:10:02, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
      2009-11-07 17:10:02, Info DISM DISM Provider Store: PID=2124 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
      2009-11-07 17:10:02, Info DISM DISM Package Manager: PID=2124 Calling into CBS through a ICbsIdentity interface to LoadFromAttributes - CPackageManagerUnattendHandler::Internal_CreateIdentityStringFromAttributes
      2009-11-07 17:10:02, Info DISM DISM Package Manager: PID=2124 Calling into CBS through a ICbsIdentity interface to SaveAsStringId - CPackageManagerUnattendHandler::Internal_CreateIdentityStringFromAttributes
      2009-11-07 17:10:02, Info DISM DISM Package Manager: PID=2124 Attempting install from source location [%configsetroot%Windows6.1-KB958559-x64.CAB]. Full path [E:AppsWindowswin2k8r2_workstationxp_modeWindows6.1-KB958559-x64Windows6.1-KB958559-x64.CAB]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to open package at location [E:AppsWindowswin2k8r2_workstationxp_modeWindows6.1-KB958559-x64Windows6.1-KB958559-x64.CAB]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to install package from source [0] - trying next source location. hr = [0x800B0100] - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to Install the package [Microsoft-Windows-VirtualPC-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7600.16393]. - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Package failed to install [Microsoft-Windows-VirtualPC-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7600.16393]. - CPackageManagerUnattendHandler::Internal_UnattendProcessPackage(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to process package at node . - CPackageManagerUnattendHandler::Apply(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Package Manager: PID=2124 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Unattend Manager: PID=2124 d:w7rtmbasentsetupopktoolsdismprovidersunattendproviderdllunattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Unattend Manager: PID=2124 d:w7rtmbasentsetupopktoolsdismprovidersunattendproviderdllunattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM Unattend Manager: PID=2124 d:w7rtmbasentsetupopktoolsdismprovidersunattendproviderdllunattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x800b0100)
      2009-11-07 17:10:03, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=800B0100
      2009-11-07 17:10:03, Info DISM DISM Image Session: PID=2124 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider DISM Package Manager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Package Manager: PID=2124 Finalizing CBS core. - CDISMPackageManager::Finalize
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider MsiManager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider IntlManager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider DriverManager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider DISM Unattend Manager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider SmiManager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider Edition Manager. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Encountered a loaded provider OSServices. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM DISM Provider Store: PID=2124 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
      2009-11-07 17:10:03, Info DISM Provider store has been disconnected. Releasing COM pointers. - CDISMImageSession::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM Provider store has been disconnected. Releasing COM pointers. - CDISMImageSession::Final_OnDisconnect
      2009-11-07 17:10:03, Info DISM Releasing the DismHostManager from the image session. - CDISMImageSession::ReleaseHostManager
      2009-11-07 17:10:03, Info DISM DISM Manager: PID=3652 Releasing references to DismHost.exe process. - CDISMManager::CloseImageSession
      2009-11-07 17:10:03, Info DISM DISMHOST.EXE: FinalRelease of DismHostManager being executed. _AtlModule lock count = 2
      2009-11-07 17:10:03, Info DISM DISMHOST.EXE: Unregistering proxy stubs.
      2009-11-07 17:10:03, Info DISM DISMHOST.EXE: Revoking DismHost class factory.
      2009-11-07 17:10:03, Info DISM DISMHOST.EXE: Completed DismHostManager release. Process should shut down. _AtlModule lock count = 1
      2009-11-07 17:10:03, Info DISM DISM Manager: PID=3652 References released. Waiting for DismHost.exe shutdown. - CDISMManager::CloseImageSession
      2009-11-07 17:10:03, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
      2009-11-07 17:10:03, Info DISM DISM.EXE:
      2009-11-07 17:10:03, Info DISM DISM.EXE: <
      Ending Dism.exe session
      >
    • #49034
      2009-11-07 17:39:18, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
      2009-11-07 17:39:18, Error CBS Failed to verify if mum file \?C:UsersADMINI~1AppDataLocalTemp7132225B-2236-4D70-87C3-06062F32E33Aupdate.mum is vouched for by catalog \?C:UsersADMINI~1AppDataLocalTemp7132225B-2236-4D70-87C3-06062F32E33Aupdate.cat. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
      2009-11-07 17:39:18, Info CBS Failed to initialize internal package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
      2009-11-07 17:39:18, Error CBS Failed to create internal package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
      2009-11-07 17:39:18, Info CBS Dism.exe returned: -2146762496
      2009-11-07 17:39:18, Info CBS pkgmgr return code: 0x800b0100

      Looks like I must also create new update.cat file…
      But there’s one small problem – I don’t know how to do it… :/

    • #49039

      @AsciiWolf wrote:

      Looks like I must also create new update.cat file…
      But there’s one small problem – I don’t know how to do it… :/

      I believe that would require some intense reverse engineering, since they are digitally signed. I’ve tried building my own simple .MSU before (i.e. a Hotfix) and it’s just about impossible. Well, it’s beyond me anyway.

      Perhaps the way to go would be to create a custom installer script in AutoIt, or in Batch + additional Command-line tools.

      EDIT: Is VirtualPC for Windows 7 and Windows XP Mode final/gold yet or still pre-release?

    • #49040

      Just a note, but have the legalities been considered?

      Windows 7 actually includes a license to use a copy of XP for xpm…this is not so for R2…..

    • #49041

      That’s a VERY good point. And the same reason why I made that post on the Windows 7 Games (in Wishlist).

      Yeah I’m going to stay out of this one… 😯 people on R2 could easily make do with VMWare Player 3.

    • #49042

      @AsciiWolf wrote:

      Looks like I must also create new update.cat file…
      But there’s one small problem – I don’t know how to do it… :/

      You can use a Hex Editor to change the original hash in update.cat, then you will need to also update the hash in _manifest_.cix.xml for update.cat.

      This will get past failure to verify the mum file, however, this invalidates the digital signature so I got:

      2009-11-11 11:47:17, Error                 CBS    Failed to verify if catalog file \?C:Userssrl1994AppDataLocalTempE93BB9A6-6B55-4084-B99F-19CB56AFD89Cupdate.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]

      I found some Windows Mobile Developer certs on my machine, so I tried signing my new .cat file with it. However, it’s not a trusted cert, so I get:

      2009-11-11 11:52:48, Error                 CBS    Failed to verify if catalog file \?C:Userssrl1994AppDataLocalTemp3803F4C8-37A5-48CC-9F1C-B1F60F1120ADupdate.cat is valid. [HRESULT = 0x800b0109 - CERT_E_UNTRUSTEDROOT]

      I have no idea how to make it trusted. It should be possible to make developer test certs and make them trusted with tools from the Windows 7 SDK, but it’s a 4GB download which will take me awhile to get.

    • #49043

      @GnatGoSplat wrote:

      I have no idea how to make it trusted. It should be possible to make developer test certs and make them trusted with tools from the Windows 7 SDK, but it’s a 4GB download which will take me awhile to get.

      Test Mode booting would then be required for x64 machines, or the ReadyDriver Plus BCD trick for unsigned driver booting. The only other way is to become a Premium MSDN member (as a developer partner) which costs a lot of money.

      I’m pretty convinced you’d have better luck making a custom installer that extracts the required files from the original source MSU, and then adds registry entries/drivers manually – rather than trying to hack the security on Windows Hotfix catalogs 😯

    • #49044

      Yeah, you may be right.
      I noticed my .cat file had an incorrect thumbprint, so I generated a new one using MakeCat.exe in the WDK.
      I was able to successfully test-sign my new .cat file and installed the new certs into Trusted Root Certification Authorities and Trusted Publishers using these instructions:
      http://www.rage3d.com/board/showthread.php?t=33920573

      I rebooted after “bcdedit /set testsigning on”, and got the “Test Mode” indication on the lower right. I clicked on my update.cat, and was pleased to see it said my catalog file is valid and certificates are OK. So I tried DISM, and in CBS.log… same problem, CERT_E_UNTRUSTEDROOT! So either DISM ignores testsigning or I did something wrong. 🙁

      A custom installer could be made, but it’s probably more complicated than I can handle. I don’t even fully understand everything the .manifest files do. I understand the file copy and registry parts, but there’s other stuff in them.

    • #49045

      A little program called InstallRite, while outrageously outdated, still works flawlessly under 2008 R2. In fact I’m using it right now to try and make a portable version of VMWare Player 3.

      http://www.epsilonsquared.com/

      Basically you can use it to take a ‘snapshot’ of the entire registry (or specific hives), and also optionally snapshot complete harddisks or specific paths – then you do whatever, install anything… change anything… reboot… heck even System Restore… then load the program and do an ‘Analyse’ and it’ll list all the changes made since the last Snapshot.

      Well System Restore might bugger it lol… but it stores it’s own database in it’s own file within the program folder, it’s completely independant of the registry as far as I know (it works without installing but you need to manually specify it’s database path if theres no reg details for the program).

      99.9% of Windows system settings are in the registry, the rest are stored as files under C:ProgramData. If you run InstallRite as administrator, it catches everything you could ever need.

      The only concern I have is that Hotfix installers tend to rely on runtime .manifest generation, because it fingerprints the install based on the current computers PID/SID or something like that. In which case, that’d be the real obstacle to overcome.

    • #49046

      Thanks for the suggestion. I spent most of yesterday playing with InstallRite, and unfortunately, I didn’t have a lot of luck with it.

      There are apparently a ton of registry settings that change regularly on their own, so I had to determine which ones apply and which ones don’t. It was a tedious task, but I managed to make a .reg file which didn’t work because many keys seemed to be missing. I ran as Administrator, but maybe I missed something? So I decided to make another attempt at reading the manifest files. I made a new .reg file which loaded, but there are 4 root kernel-mode drivers and they couldn’t be loaded. Even after setting permissions in the registry so my .reg file could write to their keys, they wouldn’t load because they’re unsigned. I guess if installed by the TrustedInstaller, it’s okay if drivers are unsigned or somehow it’s able to find the signature in the catalog file. I did also try editing the Default.iwc from InstallRite (just a renamed .mdb file), removing everything not pertaining to VirtualPC, and building an installation kit. Unfortunately, the install kit was unable to update protected registry settings nor copy files into System32 and its child folders, even when run as Administrator so I had to copy everything manually.

      Anyway, even if all the files could be copied and the registry keys added, it still won’t work because it won’t load drivers and the services that depend on them due to being unsigned, or at least that’s what I suspect. The drivers, being root drivers, don’t show up in Device Manager so I had to check the Eventlog to see that they had failed to load.

      I’m thinking best way is to somehow make a new update.cat file and find someone to legitimately sign it and install it the proper way with Windows Installer.

      On the other hand, all I wanted XP Mode for was so I can use my old USB FM tuner which has no x64 drivers available. For all this trouble, I might as well just replace it with a new one!

    • #49047
    • #49048

      @servernewbie wrote:

      Wow, nice!
      It’s based on VirtualBox but it has all the seamless stuff, original XPMode have!
      ps. If you don’t need the seamless integration, you can also (probably) use old MS Virtual PC or regular VMware/VirtualBox, if you convert the image to its format.

    • #49049

      Well, I tried it. It works great, but not everything is great…
      It’s based on VirtualBox, but it use incompatible (modified) drivers, which broke regular VirtualBox drivers. So, if I install “VMLite Workstation”, I can’t use VirtualBox any more. 🙁
      btw. Also don’t know, if this app is legal to use.

    • #49050

      All greetings.
      The register and files from XP mode windows 7 x64
      It was not tested (my system does not support virtualization 🙁 ). Access to folders overcome.
      The driver work. The test is necessary.

      http://www.filehoster.ru/files/dw0551

    • #49051

      Tested your files. Does not work.

    • #49052

      XP Mode is officially supported in Vmware (Player) 3!
      edit: The support for MS XP Mode was removed in 3.0.1, so use 3.0 only!

    • #49053

      That article is kinda moot now, since XP Mode no longer requires hardware virtualisation.

    • #49054

      Yep, but you cannot officially run XP Mode on Server 2008 R2 so this article is imho usefull for 2008 R2 Workstation users…

    • #49055

      1) VMware Workstation and Player still supports the import of XP Mode (running the 7.1 RC and see the menu “button”)
      2) Why don’t you change the 2008 R2 Workstation temporarily, so the installer think it is a Windows Seven? Atm I don’t know the right changes but for me it seems to be much easier then hacking the MSU itself. How does the MSU installer service detect the running OS version?

    • #49056

      Is it not possible to just install it into a Windows 7 machine while running a registry & file change sniffer in the background.

      once it’s done, see what changed and rip it out.

    • #49058

      update to this:

      No need to get XP Mode working, all you need is MDOP http://www.microsoft.com/windows/enterprise/products/mdop/default.aspx

    • #49057

      holy fuck… another oilpro… reminds me i need to flash my phone again later this week… (flavor of the week?)

      MDOP… interesting, will look into

    • #49059

      @FireStorm wrote:

      holy fuck… another oilpro… reminds me i need to flash my phone again later this week… (flavor of the week?)

      MDOP… interesting, will look into

      no, not another olipro, the same one.

    • #49060

      I don’t understand why MDOP should give us the solution. I’m sure you talk about MED-V, but this isn’t the same like VirtualPC and XP Mode. It needs a client – server architecture … And it isn’t available for free because you get it officially only with a corporate contract with MS.

    • #49061

      Ive got Hyper-V and all, but I still cannot figure out the one feature I want WindowsXP Mode for… USB to VPC…

      I flash my phone quite often and use various “kitchen”s to make the ROM’s, sometimes they go corrupt (file replacement and the like, totally user/base oriented) and I like to restore/uninstall/reinstall (i keep an image), but I have having to pollute the registry/file/folder trees on the main system… (infact 8 of the 24 MAIN apps I put on my system, thought they are meant for the MAIN portion, dont remove their temp files or root folders when unisntalling… Really annoying…

      Needless to say I would love to get WinXPMode working on Win2k8R2… even in lue of HyperV and the alternatives, XP Mode is just easier and faster…

      Q_Q

    • #49062

      http://en.wikipedia.org/wiki/Hyper-V … look the “Limitations” …

    • #49063

      @McStarfighter wrote:

      http://en.wikipedia.org/wiki/Hyper-V … look the “Limitations” …

      yeah i knew about MSTSC shearing, but that misses the need I have for GuestOS USB function…

      I wonder if its possible to mod the installer… meh… whatever…

    • #49064

      What I hate is the fact, that Hyper-V slows down the performance of the host (compared with a 2008R2 without Hyper-V role). You can see this very good when the UAC prompt “comes to you”. Because switching to the “Secure Desktop” shows me a black screen for ca. 2 seconds, and vice versa also.
      The big problem of this is that after installing Hyper-V the host also is a kind of virtual machine with the smaller performance …

    • #49065

      I have to say I was very disappointed with Hyper-V. Compared to the other hypervisor-based virtualisation solutions out there, Hyper-V has the ability to have the edge because it’s host-based (with a solid driver base) instead of bare-metal, but I was thoroughly disappointed by guest performance. Purely from a CPU standpoint it’s probably faster, but virtual disk I/O felt extremely slow to me, and only allowing basic VGA graphics doesn’t exactly help guest OS responsiveness either. The virtual network literally broke host network connectivity for me completely; my guess is it didn’t play nice with Intel ANS or something (I use link aggregation).

      After removing the Hyper-V role and recovering from the nightmare, I installed VMWare Workstation 7.1 and performance is just stellar– I don’t notice any slowdown from the lack of a kernel-mode hypervisor at all. The paravirtualised 3D graphics drivers are blazingly fast and everything simply works.

    • #49066

      yep… unless someone can modify the XP Mode installer, its back to VirtualPC 2007 SP1… may not have USB support like I wanted in XP Mode, but it still beats the crap out of Hyper-V…

      and like someone else said, I/O performance on Hyper-V is SHIT…

    • #49067

      @FireStorm wrote:

      and like someone else said, I/O performance on Hyper-V is SHIT…

      I don’t even get why it would be so bad. I even have Intel VT-d direct I/O or whatever the hell that is.

    • #49068

      @mufunyo wrote:

      @FireStorm wrote:

      and like someone else said, I/O performance on Hyper-V is SHIT…

      I don’t even get why it would be so bad. I even have Intel VT-d direct I/O or whatever the hell that is.

      I dont understand it either, I now have VirtualPC 2007 back on, and let met just say… HOLY SHIT…, I normally use a VPC for installing games/applications, like my Steam Library (its a gaming client if you dont know, google it!) because I dont want the host file/registry structure to get polluted, with Hyper-V I have to turn off my VPC, OFFLINE the disk I want to use, then mount it with Hyper-V then restart, BUT now I dont have access to it on the host!!! I cannot even mount it properly as a network drive!!!, anyway back to Steam, so once I refresh the downloads for my games, I always go back and do the “verify” option steam has just to make sure nothing is missed, with Hyper-V it was at 0% for 4 hours… VPC, done in 20min (TF2 was the game in question)… re-tar-ded

      XP Mode (if someone can modify the installer) or VPC ALL THE WAY…

    • #49069

      Is there any progress about creating an installer package for Windows Virtual PC on 2008 R2?

      I ask this because there is ONE 2008 R2 edition which doesn’t contain Hyper-V with it, can use 1 physical CPU, max. 8 GB RAM and is not more expensive then a Seven Home Premium (on eBay you can find it for round about 200 Euro incl. VAT)

      I talk about Windows Server 2008 R2 Foundation! IMHO this could be the best edition for a pre-modded image and also for using Windows Virtual PC on it.


      @ExpertUser
      : If you have some interest about Foundation, PM me and I give you a link for an english ISO.

    • #49070

      No feedback????? 🙁

      AsciiWolf, could you please create an installer? You would make an old man happy … 😉

    • #49071

      @McStarfighter wrote:

      @ExpertUser: If you have some interest about Foundation, PM me and I give you a link for an english ISO.

      I think Xmas came earlier for you this year !

      😆 😆 😆 😆 😆

      I hope you are enjoying your gift.

      Regards,

      ExpertUser

    • #49072

      Oh yes!

      But what I really need is Windows Virtual PC for the Workstation … 😉

    • #49073

      Is there someone who can realize it?

    • #49076
      AvatarAnonymous

      I’ll be able to start doing stuff on the wish list when I get my PC up and rolling.

      Stand by gotta wait till next week sadly when I have hardware to play around with.

      The real question is if Windows Virtual PC will install at all or if you have to do a manual install.

      What you see below is the final rig being built soon.

    • #49075

      It would be much easier to get a solution if we know how the WUSA service gets the information what OS it is. If it is only one or two registry entries then they could be modified for the installation of Virtual PC …

    • #49074
      AvatarAnonymous

      @McStarfighter wrote:

      It would be much easier to get a solution if we know how the WUSA service gets the information what OS it is. If it is only one or two registry entries then they could be modified for the installation of Virtual PC …

      Until I can actually confirm this man I’m not gonna speculate as it takes forever to do fun stuff with Windows when you start getting deep.

      Update: Laptop has arrived time to have a look

    • #49077
      AvatarAnonymous

      OK I’m having partial success with the current install here I managed to get most of the files moved over and in the right places manually instead of tinkering with the update file which would have probably taken forever.

      As of now the only issue is that when it starts there is a dll error.

      Vmwindow.exe (crash)

      Class not Registered

      So whats everything file wise being install n registered lol

    • #49078

      Windows XP Mode can be installed on Windows Server 2008 R2 through VirtualBox or VMWare Player.

      Option 1: VirtualBox

      Step 1: Download XP Mode 500MB file from Microsoft website

      Step 2: Download VirtualBox

      Step 3: Download VirtualBox VMLite plugin

      Step 4: Select XP Mode file during installation and proceed to install

      A more detailed explanation on how to do this is explained here: http://www.howtogeek.com/howto/12309/install-xp-mode-with-virtualbox-using-the-vmlite-plugin/

      Option 2: VMWare

      Step 1: Download VMWare Player
      Step 2: Click on File > Import Windows XP Mode VM

      VMWare Player will convert VHD format into compatible VMWare virtual machine disk storage.

      A more detailed step-by-step on how to do this is provided here: http://www.howtogeek.com/howto/10911/run-xp-mode-on-windows-7-machines-without-hardware-virtualization/

      Both options are free and do not break the activation of XP Mode license at all. They also do not require motherboards with hardware assisted virtualization i.e “intel VT” or anything like that.

      With the Virtualbox option you have the added bonus of creating a snapshot of your VM which is not available in VMWare Player NOR Microsoft’s Virtual PC which is the platform that runs on XP Mode.

    • #43791
      AvatarArris
      Moderator

      Description
      Get Windows XP Mode in Windows Server 2008 R2. The files needed can be downloaded from Microsoft.com – Windows XP Mode and Windows Virtual PC.

      Tried
      Nothing yet.

      Possible Hints

      • Extract and install them using expand.exe and pkgmgr.exe? After executing the commands view the Windows Update log: %SystemRoot%LogsCBSCBS.log for more details.
      • Found out that pkgmgr.exe is calling dism.exe with some parameters. After you extracted the .msu you can view all actions of the installation by using the commandline dism.exe /NoRestart /Online /LogLevel:4 /Apply-Unattend:Windows6.1-KB958559-x64.xml which logs every action to %SystemRoot%LogsDISMdism.log.
Viewing 45 reply threads
  • You must be logged in to reply to this topic.