lasky94
Apr 23, 2014, updated at Jun 02, 2014 (UTC)
view4196
view7
0
Goto Top

WinPE Treiber hinzufügen

GermansolvedQuestionMicrosoft
Hallo Miteinander

Folgendes Problem besitze ich momentan. Da wir neue Geräte bekommen haben zum Repariren (HP 840 G1), muss ich das PE Image nun Aktualisieren mit den Treiber des Gerätes. Nach anleitung habe ich es versucht es kommt immer zu folgende fehlermeldung:
C:\Programme\Windows AIK\Tools\PETools>dism /image:C:\pxe\mount /add-driver /dri
ver:C:\pxe\Treiber /recurse

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 50

The command specified is unknown or not supported when running DISM.exe against
a Windows Vista with Service Pack 1 or a Windows Server 2008 target image.
For more information, see the Help documentation available in the Windows Automa
ted Installation Kit (Windows-AIK) or the Windows OEM Preinstallation Kit (OPK).


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


Auch mit dem Logfile, ist es mir nicht gelungen dies zu lösen.

2014-04-23 10:34:58, Info                  DISM   PID=4964 Scratch directory set to 'C:\DOKUME~1\UNIQSE~1\LOKALE~1\Temp\'. - CDISMManager::put_ScratchDir  
2014-04-23 10:34:58, Info                  DISM   PID=4964 Successfully loaded the ImageSession at "C:\Programme\Windows AIK\Tools\x86\Servicing" - CDISMManager::LoadImageSession  
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Manager: PID=4964 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: 
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: 
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Host machine information: OS Version=5.1.2600, Running architecture=x86, Number of processors=2
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Executing command line: Dism /image:C:\pxe\mount /get-drivers
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Loading Provider from location C:\Programme\Windows AIK\Tools\x86\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Connecting to the provider located at C:\Programme\Windows AIK\Tools\x86\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Loading Provider from location C:\Programme\Windows AIK\Tools\x86\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Connecting to the provider located at C:\Programme\Windows AIK\Tools\x86\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Loading Provider from location C:\Programme\Windows AIK\Tools\x86\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Connecting to the provider located at C:\Programme\Windows AIK\Tools\x86\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2014-04-23 10:34:58, Info                  CSI    00000001 Shim considered [l:272{136}]"\??\C:\pxe\mount\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6001.18000_none_095f6148c74a7a64\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND  
2014-04-23 10:34:58, Info                  CSI    00000002 Shim considered [l:266{133}]"\??\C:\pxe\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6001.18000_none_095f6148c74a7a64\pkgmgr.exe" : got STATUS_SUCCESS  
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: The target image version is: 6.0.6001.18000.
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: The target image is downlevel and considered supported. Looking for PkgMgr.exe.
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Executing DISM against a downlevel image. Calling C:\pxe\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6001.18000_none_095f6148c74a7a64\pkgmgr.exe
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Getting Provider Compatibility Manager - CDISMProviderStore::GetProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2014-04-23 10:34:58, Info                  DISM   Compatibility Manager: PID=4964 Processing the top level command token(get-drivers). - CCbsCliParser::Private_ValidateCmdLine
2014-04-23 10:34:58, Info                  DISM   Compatibility Manager: PID=4964 	Unknown top level command token get-drivers - CCbsCliParser::Private_ValidateCmdLine
2014-04-23 10:34:58, Info                  DISM   Compatibility Manager: PID=4964 This command is unsupported for a downlevel image. - CCompatManager::CompatExecuteCmdLine
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: 
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2014-04-23 10:34:58, Info                  DISM   DISM.EXE: 
2014-04-23 10:34:58, Info                  DISM   DISM Image Session: PID=4964 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-04-23 10:34:58, Info                  DISM   DISM Provider Store: PID=4964 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Ausgangs Lage:
Ich habe es mit Windows 7 Pro 64 bit Ausprobiert -> Gleiches Problem
Ich habe es mit Windows XP 32 Bit ausprobiert -> Gleiches Problem
Wird nun mit windows 7 32 Bit ausprobieren
comment-contentCommentShareShare
Share on Facebook Share on Twitter Share on Reddit Share on Linkedin

Content-Key: 236219

Url: https://administrator.de/contentid/236219

Printed on: April 20, 2024 at 00:04 o'clock

7 Comments
Latest comment
Goto Top
Member: Xaero1982
Xaero1982 Apr 23, 2014 at 08:49:28 (UTC)
Goto Top
Moin,

versuche es mal damit:
http://technet.microsoft.com/de-de/library/dd744282(v=ws.10).aspx

Gruß
heart1
Member: Lasky94
Lasky94 Apr 23, 2014 at 09:01:03 (UTC)
Goto Top
Bei der Antwortdatei, muss man dies immer wieder Ausführen, dies ist leider nicht eine Lösung vom Problem welche mir helfen kann.
Da wir mehrere 100 Geräte Reaprieren, kann ich dies nicht anwenden.

Ich bedanke mich für deine Bemühung.
Member: Xaero1982
Xaero1982 Apr 23, 2014 at 09:11:45 (UTC)
Goto Top
Woher stammt denn das PE Image? Ist das schon was älter? Neues WAIK?

Gruß
Member: Lasky94
Lasky94 Apr 23, 2014 updated at 09:20:47 (UTC)
Goto Top
Problem sollte mit Windows Vista SP1 zu erledigen sein. Da ich das Image vom Arbeitskollege welcher nicht mehr im Dienst übernehmen musste, habe ich leider keine Ahnung woher es genau stammt.
Member: Xaero1982
Xaero1982 Apr 23, 2014 at 09:26:28 (UTC)
Goto Top
Im WAIK ist ein WIndows PE enthalten. Versuche es mal damit.

Die DISM Version die du benutzt habe ich auch im Einsatz. Bei mir ging das bisher problemlos.

Ich bin mir nicht sicher gerade, aber ich glaube auf einer Windows 7 DVD ist auch eine boot.wim enthalten die du dafür nutzen kannst.
Member: Tonibert
Tonibert Apr 23, 2014 at 20:46:53 (UTC)
Goto Top
Kannst du denn einzelne Treiber hinzufügen oder geht das auch nicht?Also direkt Bis zur *.inf Datei. ..mit /get-driver schauen ob die Treiber dann vorhanden sind und dann mit /commit abschließen!?
Member: Lasky94
Lasky94 Oct 21, 2014 at 20:23:37 (UTC)
Goto Top
Leider ging das nicht. Ich habe einfach alles neu gemacht und habe mir so eine menge Zeit ersparrt und nerven.
Dennoch Bedanke ich mich bei Jedem der mir Helfen wollte.
GermansolvedQuestionMicrosoft
Hotly discussed
gleixnerdCheck of ZFW Firewallgleixnerd - 3 CommentsAlexWishaHow to set up and configure a Linux GRE tunnelAlexWisha - 3 CommentsjstrickerWIREGUARD VPN ON UDM PRO BEHIND FRITZBOX - HANDSHAKE DID NOT COMPLETEjstricker - 3 CommentsDaniEnd of Support dates for Office 2016, 2019 Apps und Productivity ServersDani - 1 Comment