Powrót   Forum CDRinfo.pl > Archiwizacja - Dyski twarde, SSD, pendrive, karty pamięci > Dyski twarde, SSD - Problemy, porady, software

Dyski twarde, SSD - Problemy, porady, software Tematy dotyczące problemów, porad i oprogramowania przeznaczonego dla dysków twardych oraz SSD.



Witaj Nieznajomy! Zaloguj się lub Zarejestruj

Zarejestrowani użytkownicy mają dostęp do dodatkowych opcji, lepszej wyszukiwarki oraz mniejszej ilości reklam. Rejestracja jest całkowicie darmowa!

Odpowiedz na post
 
Opcje związane z dyskusją Ranking: Ranking dyskusji: głosów 3, średnio 4.00. Tryby wyświetlania
Stary 06.10.2013, 21:09   #1
Bartez
Team Member
Zlotowicz
 
Avatar użytkownika Bartez
 
Data rejestracji: 18.10.2002
Lokalizacja: malopolska
Posty: 4,178
Bartez jest świetnie znany wszystkim <550 - 649 pkt>Bartez jest świetnie znany wszystkim <550 - 649 pkt>Bartez jest świetnie znany wszystkim <550 - 649 pkt>Bartez jest świetnie znany wszystkim <550 - 649 pkt>Bartez jest świetnie znany wszystkim <550 - 649 pkt>Bartez jest świetnie znany wszystkim <550 - 649 pkt>
[ARTYKUŁ]Jak dodać sterowniki do ISO płyty instalacyjnej Windows 7

Cytat:
Napisany przez CDRinfo.pl


W niniejszym artykule pokażemy jak dodać sterowniki dla nowszych urządzeń (głównie mamy na myśli sterowniki do nowszych
kontrolerów SATA oraz USB 3 (...)
Zapraszamy do przeczytania artykułu: Jak dodać sterowniki do ISO płyty instalacyjnej Windows 7
Bartez jest offline   Odpowiedz cytując ten post

  #ads
CDRinfo.pl
Reklamowiec
 
 
 
Data rejestracji: 29.12.2008
Lokalizacja: Sieć globalna
Wiek: 31
Posty: 1227
 

CDRinfo.pl is online  
Stary 06.12.2013, 21:50   #2
GregoryAlone
Zarejestrowany
 
Data rejestracji: 06.12.2013
Posty: 4
GregoryAlone w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
Witam, a jeśli mam iso z wersja 32 i 64 bitowa ? To co wtedy ? czy sterowniki z usb 3.0 w wersji 64bit wystarcza aby odpalić także instalacje 32bitowa ? z tego co wiem to błąd braku sterowników wyskakuje przed wyborem wersji 32 czy 64 bitowej...
GregoryAlone jest offline   Odpowiedz cytując ten post
Stary 07.12.2013, 18:28   #3
GregoryAlone
Zarejestrowany
 
Data rejestracji: 06.12.2013
Posty: 4
GregoryAlone w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
mam problem, po tym zabiegu plik install.wim zajmuje 700MB a powinien kilka GB... :/

noi lipa, podczas instalacji windowsa z usb 3.0 nadal wola o sterowniki...

Ostatnio zmieniany przez joujoujou : 07.12.2013 o godz. 20:07 Powód: EDYTUJ NIE GRYZIE!!! To nie jest czat, tylko forum.
GregoryAlone jest offline   Odpowiedz cytując ten post
Stary 08.12.2013, 13:54   #4
gallus
gÓru
 
Avatar użytkownika gallus
 
Data rejestracji: 20.12.2003
Lokalizacja: Zbąszynek
Posty: 5,983
gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>
A czy wszystkie polecenia dotyczące integracji sterowników zakończyły się sukcesem bo wygląda na to, że nie...

Ewentualnie rozszerz komendę do
Kod:
dism /image:C:\temp\wim /add-driver /driver:. /recurse /ForceUnsigned
__________________

gallus jest offline   Odpowiedz cytując ten post
Stary 08.12.2013, 17:35   #5
GregoryAlone
Zarejestrowany
 
Data rejestracji: 06.12.2013
Posty: 4
GregoryAlone w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
Witam, dziekuje za odpowiedz

Wszystkie integracje sterownikow zakonczone sa sukcesem, nawet jesli dodam "ForceUnsigned", niby wszystko ok ale i tak występuje problem ze sterownikami sterowniki ściągam z strony producenta a laptop to msi cx61, chyba pozostaje mi instalacja z portu usb 2.0 a szkoda ;(
GregoryAlone jest offline   Odpowiedz cytując ten post
Stary 08.12.2013, 18:02   #6
gallus
gÓru
 
Avatar użytkownika gallus
 
Data rejestracji: 20.12.2003
Lokalizacja: Zbąszynek
Posty: 5,983
gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>
Nawet jak sterowniki poprawnie się zintegrują to .wim ma ~700MB?
__________________

gallus jest offline   Odpowiedz cytując ten post
Stary 08.12.2013, 18:31   #7
GregoryAlone
Zarejestrowany
 
Data rejestracji: 06.12.2013
Posty: 4
GregoryAlone w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
wcześniej używałem obrazu z dwiema wersjami 32 i 64 bit wtedy miał 700MB, jak użyłem obrazu z jedna wersja wtedy .wim jest ok..
GregoryAlone jest offline   Odpowiedz cytując ten post
Stary 08.12.2013, 20:15   #8
gallus
gÓru
 
Avatar użytkownika gallus
 
Data rejestracji: 20.12.2003
Lokalizacja: Zbąszynek
Posty: 5,983
gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>gallus jak się przyłoży ma szansę zostać specem <150 - 249 pkt>
Spróbuj może DISM GUI, sam jestem ciekaw ale niestety nie mam obrazu W7 z x32 + x64...
__________________

gallus jest offline   Odpowiedz cytując ten post
Stary 31.12.2013, 14:17   #9
Misiek4
____
 
Avatar użytkownika Misiek4
 
Data rejestracji: 26.05.2000
Lokalizacja: Tarnow
Posty: 1,738
Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>
Do artykułu dodaliśmy opis w jaki sposób zintegrować sterowniki z systemem Windows 7/8 za pomocą narzędzia Win Toolkit. Cała operacja jest znacznie łatwiejsza i zdecydowanie szybsza.

Ponadto Win Toolkit posiada mnóstwo opcji pozwalających na dopasowanie danej instalacji do własnych potrzeb, m.in. pozwala na dodanie własnych programów, gadżetów, tapet, integrację uaktualnień, zmianę/dodanie numerów seryjnych, usunięcie niektórych komponentów, połączenie systemów 32 i 64-bitowych, etc.
__________________
Pozdrawiam
Misiek4

Wydaje Ci się, że masz szybki dysk twardy/SSD? Dodaj go do rankingu i sprawdź czy jest najszybszy .
Misiek4 jest offline   Odpowiedz cytując ten post
Stary 10.11.2015, 06:12   #10
Nornik
Zarejestrowany
 
Data rejestracji: 09.11.2015
Lokalizacja: Warszawa
Posty: 8
Nornik w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
Mam małe pytanko - czy należy dodawać całe foldery ze sterownikami zarówno USB jak i SATA, tego jest dużo jak rozpakowałem po ściągnięciu ? Czy ręcznie wybrać jak pokazane jest na obrazku w artykule ?
Nornik jest offline   Odpowiedz cytując ten post
Stary 10.11.2015, 08:56   #11
Misiek4
____
 
Avatar użytkownika Misiek4
 
Data rejestracji: 26.05.2000
Lokalizacja: Tarnow
Posty: 1,738
Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>Misiek4 jest klejnotem wśród średnio znających się "w temacie" <250 - 349 pkt>
Trudno jednoznacznie odpowiedzieć. Wrzuciłbym całość i się nie przejmował wielkością katalogów.
__________________
Pozdrawiam
Misiek4

Wydaje Ci się, że masz szybki dysk twardy/SSD? Dodaj go do rankingu i sprawdź czy jest najszybszy .
Misiek4 jest offline   Odpowiedz cytując ten post
Stary 15.09.2018, 14:09   #12
Arvir
Zarejestrowany
 
Data rejestracji: 15.09.2018
Posty: 1
Arvir w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
Dodanie sterownikow do install.wim

Witam .
Działałem według powyzszego poradnika i dograłem potrzebne sterowniki do pliku boot.wim (komunikat :instalacja przebiegła pomyślnie ), jednak gdy probowalem powtorzyc operacje z plikiem install.wim dostaje informacje :Wystapił bład. Nie można zainstalować pakietu sterowników . Bład :15105
Probowałem sterowników 32 i 64 bit (na tym etapie to chyba nie ma znaczenia ) Dodawałem rownież do komendy /forceunsigned oraz /recurse .
W logu programu DISM wyglada to tak :


2018-09-15 14:00:24, Info DISM DISM.EXE: Executing command line: dism /image:mount /add-driver /driver:usb3 /recurse /forceunsigned
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:24, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-09-15 14:00:24, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2018-09-15 14:00:24, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2018-09-15 14:00:24, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2018-09-15 14:00:24, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-09-15 14:00:24, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2018-09-15 14:00:24, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2018-09-15 14:00:24, Info DISM DISM Provider Store: PID=2164 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-15 14:00:25, Info DISM DISM Provider Store: PID=2164 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-15 14:00:27, Info DISM DISM Manager: PID=2164 Successfully loaded the ImageSession at "C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D" - CDISMManager::LoadImageSession
2018-09-15 14:00:27, Info DISM DISM Image Session: PID=4972 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-09-15 14:00:27, Info DISM DISM Provider Store: PID=4972 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-09-15 14:00:27, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:27, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:27, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:27, Info DISM DISM OS Provider: PID=4972 Defaulting SystemPath to C:\win7\mount - CDISMOSServiceManager::Final_OnConnect
2018-09-15 14:00:27, Info DISM DISM OS Provider: PID=4972 Defaulting Windows folder to C:\win7\mount\Windows - CDISMOSServiceManager::Final_OnConnect
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Warning DISM DISM Provider Store: PID=4972 Failed to Load the provider: C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007 007e)
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Manager: PID=2164 Image session successfully loaded from the temporary location: C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D - CDISMManager::CreateImageSession
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM OS Provider: PID=4972 Setting SystemPath to C:\win7\mount - CDISMOSServiceManager::SetSystemPath
2018-09-15 14:00:35, Info CSI 00000001 Shim considered [l:278{139}]"\??\C:\win7\mount\Windows\Servicing\amd64_microso ft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-09-15 14:00:35, Info CSI 00000002 Shim considered [l:272{136}]"\??\C:\win7\mount\Windows\WinSxS\amd64_micros oft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-09-15 14:00:35, Info DISM DISM.EXE: Target image information: OS Version=6.1.7601.17514, Image architecture=amd64
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:35, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:35, Info CSI 00000001 Shim considered [l:278{139}]"\??\C:\win7\mount\Windows\Servicing\amd64_microso ft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-09-15 14:00:35, Info CSI 00000002 Shim considered [l:272{136}]"\??\C:\win7\mount\Windows\WinSxS\amd64_micros oft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-09-15 14:00:36, Info DISM DISM Package Manager: PID=4972 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-09-15 14:00:36, Info CSI 00000001 Shim considered [l:278{139}]"\??\C:\win7\mount\Windows\Servicing\amd64_microso ft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-09-15 14:00:36, Info CSI 00000002 Shim considered [l:272{136}]"\??\C:\win7\mount\Windows\WinSxS\amd64_micros oft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-09-15 14:00:36, Info CBS Failed to find a matching version for servicing stack: C:\win7\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-09-15 14:00:36, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-09-15 14:00:36, Info CBS Must be doing offline servicing, using stack version from: C:\win7\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\cbscore.dll
2018-09-15 14:00:36, Info CBS Loaded Servicing Stack v6.1.7601.17514 with Core: C:\win7\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\cbscore.dll
2018-09-15 14:00:36, Info CSI 00000001@2018/9/15:12:00:36.095 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee473e94d @0x7fee5b49839 @0x7fee5b134d3 @0x7fee5c270b9 @0x7fee5c272a7 @0x7fee5bf8843)
2018-09-15 14:00:36, Info CSI 00000002@2018/9/15:12:00:36.099 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee473e94d @0x7fee5b96806 @0x7fee5b62a9c @0x7fee5b135a9 @0x7fee5c270b9 @0x7fee5c272a7)
2018-09-15 14:00:36, Info DISM DISM Package Manager: PID=4972 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-09-15 14:00:36, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SOFTWARE' from path '\\?\C:\win7\mount\Windows\System32\config\SOFTWAR E'.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SYSTEM' from path '\\?\C:\win7\mount\Windows\System32\config\SYSTEM' .
2018-09-15 14:00:36, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SECURITY' from path '\\?\C:\win7\mount\Windows\System32\config\SECURIT Y'.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SAM' from path '\\?\C:\win7\mount\Windows\System32\config\SAM'.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/COMPONENTS' from path '\\?\C:\win7\mount\Windows\System32\config\COMPONE NTS'.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/DEFAULT' from path '\\?\C:\win7\mount\Windows\System32\config\DEFAULT '.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Users/default/ntuser.dat' from path '\\?\C:\win7\mount\Users\default\ntuser.dat'.
2018-09-15 14:00:36, Info CBS Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/system32/smi/store/Machine/schema.dat' from path '\\?\C:\win7\mount\Windows\system32\smi\store\Mach ine\schema.dat'.
2018-09-15 14:00:36, Info CBS Offline image is: writeable
2018-09-15 14:00:36, Info CSI 00000003 CSI Store 4073232 (0x00000000003e2710) initialized
2018-09-15 14:00:36, Info CBS Session: 4972_1358784 initialized by client DISM Package Manager Provider.
2018-09-15 14:00:36, Info DISM DISM Package Manager: PID=4972 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-09-15 14:00:36, Info DISM DISM Package Manager: PID=4972 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-09-15 14:00:36, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:36, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:36, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:36, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info CSI 00000001 Shim considered [l:278{139}]"\??\C:\win7\mount\Windows\Servicing\amd64_microso ft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-09-15 14:00:37, Info CSI 00000002 Shim considered [l:272{136}]"\??\C:\win7\mount\Windows\WinSxS\amd64_micros oft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_non e_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-09-15 14:00:37, Info DISM DISM OS Provider: PID=4972 Get the registry path to the SOFTWARE hive located at C:\win7\mount\Windows\system32\config\SOFTWARE and determine if it is loaded. - CDISMOSServiceManager:etermineBootDrive
2018-09-15 14:00:37, Info DISM DISM Driver Manager: PID=4972 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Loading Provider from location C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Connecting to the provider located at C:\Users\DziubSon\AppData\Local\Temp\DDB4966B-279E-4A38-AFFD-4BFD4BFB356D\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-09-15 14:00:37, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-09-15 14:00:37, Info DISM DISM Transmog Provider: PID=4972 Current image session is [OFFLINE] - CTransmogManager::GetMode
2018-09-15 14:00:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Getting Provider DriverManager - CDISMProviderStore::GetProvider
2018-09-15 14:00:37, Info DISM DISM Provider Store: PID=4972 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-09-15 14:00:37, Info DISM DISM Driver Manager: PID=4972 Driver C:\win7\usb3\iusb3hub.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2018-09-15 14:00:37, Info IsDriverPackageSigned: File [C:\win7\usb3\iusb3hub.inf] is signed by a catalog [C:\win7\usb3\iusb3hub.cat]
2018-09-15 14:00:37, Info DISM DISM Driver Manager: PID=4972 Signature status of driver C:\win7\usb3\iusb3hub.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2018-09-15 14:00:37, Info DISM DISM Driver Manager: PID=4972 Driver C:\win7\usb3\iusb3xhc.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2018-09-15 14:00:37, Info IsDriverPackageSigned: File [C:\win7\usb3\iusb3xhc.inf] is signed by a catalog [C:\win7\usb3\iusb3xhc.cat]
2018-09-15 14:00:37, Info DISM DISM Driver Manager: PID=4972 Signature status of driver C:\win7\usb3\iusb3xhc.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 Failed to install the driver package 'C:\win7\usb3\iusb3hub.inf'. - CDmiDriverStore::Import(hr:0x80073afc)
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 Failed to install the driver package 'C:\win7\usb3\iusb3hub.inf'. - CDriverPackage::InternalInstall(hr:0x80073afc)
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmip rovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80073afc)
2018-09-15 14:00:38, Info DISM DISM Driver Manager: PID=4972 Driver package C:\win7\usb3\iusb3hub.inf failed to install. (hr:0x80073afc). - CDriverManager::AddDriverPackagesFromCollection
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 Failed to install the driver package 'C:\win7\usb3\iusb3xhc.inf'. - CDmiDriverStore::Import(hr:0x80073b01)
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 Failed to install the driver package 'C:\win7\usb3\iusb3xhc.inf'. - CDriverPackage::InternalInstall(hr:0x80073b01)
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmip rovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80073b01)
2018-09-15 14:00:38, Info DISM DISM Driver Manager: PID=4972 Driver package C:\win7\usb3\iusb3xhc.inf failed to install. (hr:0x80073b01). - CDriverManager::AddDriverPackagesFromCollection
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmip rovider\dll\drivermanager.cpp:1063 - CDriverManager::Internal_DoAddDriverPackage(hr:0x8 0073b01)
2018-09-15 14:00:38, Error DISM DISM Driver Manager: PID=4972 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmip rovider\dll\drivermanager.cpp:519 - CDriverManager::ExecuteCmdLine(hr:0x80073b01)
2018-09-15 14:00:38, Info DISM DISM Driver Manager: PID=4972 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::ExecuteCmdLine
2018-09-15 14:00:38, Info DISM DISM Image Session: PID=4972 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SOFTWARE
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SYSTEM
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SECURITY
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SAM
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/COMPONENTS
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/DEFAULT
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Users/default/ntuser.dat
2018-09-15 14:00:38, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Users/default/ntuser.dat, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-09-15 14:00:38, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/win7/mount/Windows/system32/smi/store/Machine/schema.dat
2018-09-15 14:00:38, Info DISM DISM Package Manager: PID=4972 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM OS Provider: PID=4972 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2018-09-15 14:00:38, Info DISM DISM Provider Store: PID=4972 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-09-15 14:00:38, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2018-09-15 14:00:38, Info DISM DISM.EXE:
2018-09-15 14:00:38, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->


Wie ktoś może jakie jest rozwiazanie tego problemu ? Czym może roznić sie plik boot.wim od install.wim że na tym pierwszym instaluje sie bez problemu a na drugim wywala błedy . Z gory dzięki za pomoc
Arvir jest offline   Odpowiedz cytując ten post
Stary 12.12.2021, 21:40   #13
LukeSlovian
Zarejestrowany
 
Data rejestracji: 11.12.2021
Posty: 4
LukeSlovian w tym momencie nie ma Reputacji dodatnich ani ujemnych <0  pkt>
Question

Witam czy mógłbym otrzymać poradnik jak szybkimi ustawieniami w Windows 10 wprowadzić sobie odblokowanie tworzenia nośnika ISO ze zintegrowanymi sterownikami. Informuje że podążam według tego poradnika Dodanie sterowników do instalki Windows 7 - metoda 1

Informuje że jestem nowy i nie mam jak dodać linku do poradnika z portalu cdrinfo.
Dołączone obrazki (kliknij, aby powiększyć)
-img_2179.jpg.8800668138471f5bf8040f6884864ce2-1-.jpg  
LukeSlovian jest offline   Odpowiedz cytując ten post
Odpowiedz na post

Tagi
integracja sterownikow, sterowniki, windows 7, windows 7 sterowniki

Opcje związane z dyskusją
Tryby wyświetlania Oceń tę dyskusję
Oceń tę dyskusję:

Twoje uprawnienia:
Nie możesz rozpoczynać nowych tematów
Nie możesz odpowiadać w tematach
Nie możesz umieszczać załączników
Nie możesz edytować swoich postów

BB codeWłączone
EmotikonkiWłączone
Kody [IMG]Włączone
Kody HTML są Wyłączone

Teleport

Podobne dyskusje
Dyskusja Autor Forum Odpow. Ostatni Post
program do stworzenia własnej płyty instalacyjnej WODZU1972 Komputery - oprogramowanie i sprzęt 3 29.06.2008 02:58
Windows nie widzi nagranej płyty UDF klosz007 Napędy optyczne DVD 3 22.01.2006 15:47
Dogrywanie plików do płyty instalacyjnej Win XP kajtom Napędy optyczne CD 4 01.11.2005 07:56
Aktualizacje Windows 98/Me/2k Piterniel Off topic 4 05.06.2005 22:54
iso płyty Kowal Napędy optyczne CD 3 02.04.2001 02:09


Wszystkie czasy w strefie CET. Aktualna godzina: 14:14.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.