Wiewson Opublikowano 3 Maja 2018 Zgłoś Udostępnij Opublikowano 3 Maja 2018 Hejka przypadkiem posypała mi się tablica dla UEFIjak próbuję przywrócić Tutkami to zawsze na końcu mam wyniknie znaleziono żadnych instalacji windowsCzy ktokolwiek był by w stanie pomóc? w logu SrtTrial jest że mountmgr.sys jest uszkodzonychkdsk ruszył i poprawił to i owo sfc nie czyta dysku i "windows resorce protection"diskpart, attrib disk i vol, read only = no nie wiem co zrobić bcdtedit pokazuje Windows Booot Menager-------------------------------------------------------identifier {bootmgr}path \EFI\Microsoft\Boot\bootmgfw.efidescription Windows Boot Managerlocale en-USintherit {globalsetings}default {default}device partition=C:resumobject {8f8ee6a-4a80-11e8-9620-e8ffcbeeffa7}displayorder {default}toolsDisplayorder {memdiag}timeout 30 Windows Booot Loader--------------------------------------------------------identifier {default}device partition=C:path \windows\system32\winload.efidescription Windows 10locale en-USinhereit {bootloadersetings}isolocatedcontext Yesallowmemorysetings 0x15000075osdevice particion=C:systemroot \windowsresumeobject {8f8ee6a-4a80-11e8-9620-e8ffcbeeffa7}nx OptInbootmenuplicy Standardjęzyk to akurta mam w systemie PL Odnośnik do komentarza
Wiewson Opublikowano 3 Maja 2018 Autor Zgłoś Udostępnij Opublikowano 3 Maja 2018 ## Windows Boot Manager identifier {bootmgr} device partition=C: description Windows Boot Manager locale en-US inherit {globalsettings} default {current} displayorder {current} {18b123cd-2bf6-11db-bfae-00e018e2b8db} toolsdisplayorder {memdiag} timeout 30 ## Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Microsoft Windows Vista locale en-US inherit {bootloadersettings} osdevice partition=C: systemroot \Windows resumeobject {d7094401-2641-11db-baba-00e018e2b8db} nx OptIn ## Windows Boot Loader ------------------- identifier {18b123cd-2bf6-11db-bfae-00e018e2b8db} device partition=C: path \Windows\system32\winload.exe description Debugger Boot locale en-US inherit {bootloadersettings} osdevice partition=C: systemroot \Windows resumeobject {d7094401-2641-11db-baba-00e018e2b8db} nx OptIn debug Yes Czy tak powinien wyglądać poprawnie zbudowany boot? Bo nie wiem czy się nie zagalopowałem. https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/adding-boot-entries https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcd-system-store-settings-for-uefi Odnośnik do komentarza
Wiewson Opublikowano 20 Maja 2018 Autor Zgłoś Udostępnij Opublikowano 20 Maja 2018 hej czy ktoś ogarnie może to?X:\WINDOWS>dism /image:c:\offline /cleanup-image /restorehealth /source:d:\sources\install.wim /LimitAccessError: 2Unable to access the image.Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.The DISM log file can be found at X:\windows\Logs\DISM\dism.log DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager2018-05-21 00:47:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager2018-05-21 00:47:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.2018-05-21 00:47:21, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager2018-05-21 00:47:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection2018-05-21 00:47:21, Error DISM FolderManager: PID=1532 onecore\base\ntsetup\opktools\dism\providers\folderprovider\dll\folderimage.h:190 - CFolderImage::CreateFolderImage(hr:0x80070032)2018-05-21 00:47:21, Info DISM DISM WIM Provider: PID=1532 TID=1536 [c:\offline] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize2018-05-21 00:47:21, Info DISM DISM VHD Provider: PID=1532 TID=1536 [c:\offline] is not recognized by the DISM VHD provider. - CVhdImage::Initialize2018-05-21 00:47:21, Warning DISM DISM Provider Store: PID=1532 TID=1536 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)2018-05-21 00:47:21, Info DISM DISM VHD Provider: PID=1532 TID=1536 [c:\offline] is not recognized by the DISM VHD provider. - CVhdImage::Initialize2018-05-21 00:47:21, Info DISM DISM Imaging Provider: PID=1532 TID=1536 The provider VHDManager does not support CreateDismImage on c:\offline - CGenericImagingManager::CreateDismImage2018-05-21 00:47:21, Info DISM DISM WIM Provider: PID=1532 TID=1536 [c:\offline] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize2018-05-21 00:47:21, Info DISM DISM Imaging Provider: PID=1532 TID=1536 The provider WimManager does not support CreateDismImage on c:\offline - CGenericImagingManager::CreateDismImage2018-05-21 00:47:21, Info DISM DISM Imaging Provider: PID=1532 TID=1536 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage2018-05-21 00:47:21, Error DISM DISM.EXE: Failed to access the image folder or image's windows folder.2018-05-21 00:47:21, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.2018-05-21 00:47:21, Info DISM DISM.EXE:2018-05-21 00:47:21, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->2018-05-21 00:47:21, Info DISM DISM.EXE:2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider2018-05-21 00:47:21, Info DISM DISM Provider Store: PID=1532 TID=1536 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProviderSFCfix nie uruchamia mi się, lub robię coś nie właściwie Odnośnik do komentarza
maggreg Opublikowano 21 Maja 2018 Zgłoś Udostępnij Opublikowano 21 Maja 2018 Opcja /cleanup-image działa na zamontowanym obrazie a nie na pliku obrazu (.wim). Najpierw /Mount-Image albo /Mount-Wim. pzdr Odnośnik do komentarza
Rekomendowane odpowiedzi
Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto
Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.
Zarejestruj nowe konto
Załóż nowe konto. To bardzo proste!
Zarejestruj sięZaloguj się
Posiadasz już konto? Zaloguj się poniżej.
Zaloguj się