Dism ошибка 267 не удалось получить доступ к образу - Ремонт и установка крупной бытовой техники

Hello,

I have been runing Windiws AIK for some time now and have had very little problems with it the last few days. I am trying to update the Windows PE disk that is part of Windows AIK for windows 7 and I keep gettign the following error: «Error:
267 Unable 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 command I am using is «dism /Image:c:temptestwinpe.wim /Get-Drivers». I have done this many time before nad it works just fine but in the last few days it has not.

Here is the information from the DISM log file:

2011-04-19 11:22:02, Info                  DISM   PID=5292 Scratch directory set to ‘C:Usersabatson.ADAppDataLocalTemp’. — CDISMManager::put_ScratchDir
2011-04-19 11:22:02, Info                  DISM   PID=5292 Successfully loaded the ImageSession at «C:Program FilesWindows AIKToolsAMD64Servicing» — CDISMManager::LoadImageSession
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeLogger
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Failed to get and initialize the PE Provider. Continuing by assuming that it
is not a WinPE image. — CDISMProviderStore::Final_OnConnect
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has previously been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has previously been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Manager: PID=5292 Successfully created the local image session and provider store. — CDISMManager::CreateLocalImageSession
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has previously been initialized. Returning the existing instance. —
CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM.EXE:

2011-04-19 11:22:02, Info                  DISM   DISM.EXE: <—— Starting Dism.exe session ——>
2011-04-19 11:22:02, Info                  DISM   DISM.EXE:

2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Executing command line: dism /Image:c:temptestwinpe.wim /Get-Drivers
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Getting the collection of providers from a local provider store type. — CDISMProviderStore::GetProviderCollection
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has not previously been encountered. Attempting to initialize the provider.
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Loading Provider from location C:Program FilesWindows AIKToolsAMD64ServicingWimProvider.dll
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Connecting to the provider located at C:Program FilesWindows AIKToolsAMD64ServicingWimProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has not previously been encountered. Attempting to initialize the provider.
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Loading Provider from location C:Program FilesWindows AIKToolsAMD64ServicingFolderProvider.dll
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Connecting to the provider located at C:Program FilesWindows AIKToolsAMD64ServicingFolderProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Provider has not previously been encountered. Attempting to initialize the provider.
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Loading Provider from location C:Program FilesWindows AIKToolsAMD64ServicingCompatProvider.dll
— CDISMProviderStore::Internal_GetProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Connecting to the provider located at C:Program FilesWindows AIKToolsAMD64ServicingCompatProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2011-04-19 11:22:02, Error                 DISM   DISM.EXE: Failed to access the image folder or image’s windows folder.
2011-04-19 11:22:02, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2011-04-19 11:22:02, Info                  DISM   DISM.EXE:

2011-04-19 11:22:02, Info                  DISM   DISM.EXE: <—— Ending Dism.exe session ——>
2011-04-19 11:22:02, Info                  DISM   DISM.EXE:

2011-04-19 11:22:02, Info                  DISM   DISM Image Session: PID=5292 Disconnecting the provider store — CDISMImageSession::Final_OnDisconnect
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Disconnecting Provider: WimManager — CDISMProviderStore::Internal_DisconnectProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Disconnecting Provider: FolderManager — CDISMProviderStore::Internal_DisconnectProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Found the OSServices. Waiting to finalize it until all other providers are unloaded.
— CDISMProviderStore::Final_OnDisconnect
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Disconnecting Provider: Compatibility Manager — CDISMProviderStore::Internal_DisconnectProvider
2011-04-19 11:22:02, Info                  DISM   DISM Provider Store: PID=5292 Releasing the local reference to DISMLogger. Stop logging. — CDISMProviderStore::Internal_DisconnectProvider

I have check the file ACLs and I do have access to the file and I am login in as the Administrator. Note, I can mount the WinPE image file no problem with DISM commands and I can created and burn it as an ISO with our problem. Yes, the
ISO will boot a PC and work just fine. I just cannot get and any driver information or add any driver (which is what I need to do).

Any ideas?

~Thanks,

Dyslextic

Источник

Hello,

The command I am using is «dism /Image:c:temptestwinpe.wim /Get-Drivers». I have done this many time before nad it works just fine but in the last few days it has not.

Here is the information from the DISM log file:

Any ideas?

~Thanks,

Dyslextic

Источник

You have DISM error 267, “unable to access the image,” but you do not know how to resolve it. This article describes what causes DISM error 267 and how to resolve it. Before demonstrating how to resolve the issue, I will explain why you received the error notice.
It may be found in my first section.

Once you have determined the reason for DISM error 267, you may utilize the three methods outlined in section two to resolve the problem message. I also have a Frequently Asked Questions area where I address several inquiries regarding DISM, notably Error 267.

Why Did You Receive DISM Error 267 “Cannot Access The Image”?

You will receive error 267 if you execute the DISM command with the /image switch directly on a WIM, VHD, or VHDX file.
Because DISM expects a mounted image, this error occurs.

In my situation, I received error 267 when I executed the following DISM command.

DISM /image:"F:sourcesinstall.wim" /?

Here is the command’s output.

This error notice can be resolved by mounting the WIM, VHD, or VHDX file. Then, execute the preceding DISM command and provide the location where the image file was mounted.

In the next step, I describe how to resolve DISM error 267.

How to Repair DISM Error 267 Unable To View The image. Follow the procedures in this section to correct DISM error 267, “unable to access the image.” In this section, each stage is discussed in its part.

Perform Pre-Task Requirements

Before continuing, please complete the following:

The Windows image (WIM, VHD, or VHDX) should be copied to a folder. If you interact with them, Microsoft puts WIM files in the Windows installation media sources folder. Microsoft refers to the WIM file installation as an install.
WIM. You should replicate the installation. WIM from the sources folder to a different folder since mounting the file from its original read-only location may result in an access forbidden error. Create a folder in which to mount the Windows image. My folder will be named Windows11MountDir.
I am doing the example in this article using an installation of Windows 11. WIM file. The instructions in this article can also be used to mount a VHD or VHDX file. When working with these kind of files, copy them to a different place. Then, create a folder where the Windows image will be mounted.

Retrieve The Windows Image Index

Before you can mount a Windows image, you must have the image’s index number or name. To obtain the index of a Windows image, use Command Prompt as an administrator and then enter the following command:

DISM /Get-WimInfo /WimFile:D:WIMfilesinstall.wim

Replace D:WIMfiles with the full path of your file.
The function reveals the specifics of all Windows images included within a WIM, VHD, or VHDX file. Take note of the index number of the edition that you wish to mount.

I will mount “Windows 11 Pro” in this example; its index number is 6.

Mount The Windows Image And Then Run DISM /Image Again

Mounting the Windows image is the last step in correcting DISM error 267, “unable to access the image.” To mount the Windows image using the index number indicated in the previous step, use a command identical to the one shown below:

DISM /Mount-image /imagefile:D:WIMfilesinstall.wim /Index:6 /MountDir:"D:Windows11MountDir"

Replace D:WIMfiles with the location where you stored your file. Then, replace D: Windows11MountDir with the mount folder you previously established.
When the command is executed, it will take some time to complete.

When the command completes, open the folder where the image was mounted. The folder hierarchy will resemble a standard Windows installation folder.

Lastly, to resolve DISM error 267, “unable to access the image,” execute DISM using the /image switch. However, instead of supplying the path to the Windows image, mention the folder directory where the Windows image was mounted.

I have mounted my Windows image (a WIM file) at D: Windows11MountDir; thus, I will execute the following command.

The command DISM /image:D:Windows11MountDir /?

As shown in the image below, the DISM command was completed properly without error 267 this time!

When you are finished working with a mounted image, it is advisable to unmount it. To unmount the image and save the modifications, use the command below.

DISM /Unmount-image /MountDir:D:Windows11MountDir /commit

Microsoft Windows 11 Mount Directory /commit

However, if you desire to discard any modifications you made to the picture or if no changes were made, use the command below.

DISM /Unmount-image /MountDir:D:Windows11MountDir /discard

Windows11MountDir/reject
Remember to alter the directory – D:
Windows11MountDirM – to the directory where the image was mounted.

Frequently Asked Questions:

What is DISM used for?

DISM is a command-line utility for servicing and preparing Windows Operating System images. You may use DISM to service an operating system currently running and a Windows image.

How can I resolve DISM errors?

Since DISM contains several potential faults, the most straightforward approach to repair any DISM mistake is to examine the DISM error log – C:WINDOWSLogsDISMdism.log – as a starting point.
Scroll to the bottom of the dism.log file to view the most recent logs. When you examine the logs, you will be able to determine the source of the DISM problem.

What does the DISM command with the /ScanHealth option accomplish?

When /ScanHealth is passed to DISM, the Windows image is scanned for component store corruption. To execute DISM with the /ScanHealth switch, the /Cleanup-Image switch must be specified.

Here is the complete command to scan for component store corruption on a running operating system…

Does DISM Need a Restart?

Perhaps not necessarily. Some DISM commands may necessitate a system restart, while others do not.

What Is the DISM.EXE /Online /Cleanup-image /Restorehealth Command?

The /Online switch instructs DISM to execute the /Cleanup-image /Restorehealth command on the currently running Operating System.
The /Cleanup-image option with the /Restorehealth parameter further searches the image for component store corruption.
Using the /Cleanup-image /Restorehealth option and argument, the idea is automatically repaired once DISM scans the Windows image for compone’nt store corruption.

My Last Words:

The inability to access the picture is one of the several DISM error signals. As detailed in this tutorial, DISM raises error 267 when the /image switch is applied to an unmounted image when running the DISM command.

ALSO SEE:Best FAQs Related To Apple iPhone 14 Pro and 14 Pro Max

Also, as demonstrated in this article, mounting the Windows image before executing the DISM command with the /image option resolves DISM error 267.

Источник

win10ltsb
Ошибка: 2
Не удалось получить доступ к образу.
Убедитесь, что путь к образу и каталог Windows образа существуют и учетная запись обладает правами на чтение папки.

захожу в винду в режиме восстановления через коммандную строку, ввожу (учетка администратора встроенного)

DISM /Image:C /Cleanup-Image /RestoreHealth /Source:WIM:C:install.wim /scratchdir:D:1
wim находится в корне C, Ос там же
Что делаю не так?

лог

Источник

Windows 10: DISM error 267 when trying to add drivers to WinPE setup

Discus and support DISM error 267 when trying to add drivers to WinPE setup in Windows 10 Gaming to solve the problem; Hello, I’m trying create a new image and I’m having issues running basic DISM commands following MS documentation. This same documentation has worked…
Discussion in ‘Windows 10 Gaming’ started by Jaded Son, Dec 8, 2021.

DISM error 267 when trying to add drivers to WinPE setup

Hello, I’m trying create a new image and I’m having issues running basic DISM commands following MS documentation. This same documentation has worked before without issue. Not sure what I’m missing or doing wrong. Error 267 — «Unable 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.» I’ve confirmed that I have full permissions to .WIM file I have full admin permissions on my system. I’m using the correct paths I’ve tried many different commands, all produce this error. I’m able to boot into the
Add packages to WinPE version 10.0.15063.0

I am unable to add any packages to my WinPE wim file using DISM.

I consistently get the following error:

Error: 0x800f081e

The specified package is not applicable to this image

Does anyone have any suggestions or workarounds?
DISM — Add or Remove Drivers on an Offline Image

Ah I thought you might be doing the DISM/drivers one.

It is good info and I use parts of this frequently when I’m reinstalling on my old hardware and need to manually add drivers.

I would suggest DISM /Get-Drivers as an alternate to the Powershell step in 2.2 — the table format is quite useful I find.

One method of applying the drivers I tried which seems to work (not sure how valid it is) when clean-installing a machine as a one-off:
1. Export drivers as per Step 2
2. Use DISM /Get-Drivers to show which driver is which, and copy only the ones I know are problematic to a subfolder, and add this subfolder to a bootable Windows 10 Setup USB
3. Boot Windows 10 Setup from the USB
4. Open a command prompt with Shift F10, type command ‘wpeutil shutdown’ but don’t press enter. Instead, Alt-Tab back to Setup
5. Follow the normal clean install process, delete partitions and let it install the relevant edition
6. When it says Restarting in a few seconds, quickly Alt-Tab to the command prompt and press enter, to stop it restarting but shut down instead
7. Boot again from the USB, go straight into Shift-F10, and use DISM /add-driver to add relevant drivers to the offline Windows drive as per Step 4
8. wpeutil shutdown again, and let it restart this time, so that Windows boots and finishes configuring itself with the new drivers available to it.
I found it easier than Mounting the image and also means I don’t change the .WIM so I can use that on other hardware without fear of non-standard (and probably quite old) drivers getting in the way .

Although in some cases I could install and change it once Windows is up and running , one of 1709’s default drivers causes a BSOD during installation itself, if I don’t add the alternative manually using the above technique before it gets to that point.

But it’s not a technique I’ve seen anywhere else so I’m probably bending the rules somewhere. *Wink
DISM error 267 when trying to add drivers to WinPE setup

Force load MS Generic SD Card Reader Drivers in WinPE

Thank you for the response .. however, neither link supplied is very helpful to me. I already know how to add drivers to WinPE using DISM or how to load them after WinPE has booted using DRVLOAD .. problem is neither of these are working.

Thema:

DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup — Similar Threads — DISM error 267
DISM error 0x800f080a, trying to update manually .cab add package

in Windows 10 Gaming

DISM error 0x800f080a, trying to update manually .cab add package: I got dism error 0x80f080a, I tried add package cab, correctly x64 and latest version 20H2 package, while my system is running Windows 10 21H1 virtual machine on Powershell. Here is log file:https://pastebin.com/qvTRUXdr…
DISM error 0x800f080a, trying to update manually .cab add package

in Windows 10 Software and Apps

DISM error 0x800f080a, trying to update manually .cab add package: I got dism error 0x80f080a, I tried add package cab, correctly x64 and latest version 20H2 package, while my system is running Windows 10 21H1 virtual machine on Powershell. Here is log file:https://pastebin.com/qvTRUXdr…
DISM error 0x800f080a, trying to update manually .cab add package

in Windows 10 Installation and Upgrade

DISM error 0x800f080a, trying to update manually .cab add package: I got dism error 0x80f080a, I tried add package cab, correctly x64 and latest version 20H2 package, while my system is running Windows 10 21H1 virtual machine on Powershell. Here is log file:https://pastebin.com/qvTRUXdr…
DISM error 267 when trying to add drivers to WinPE setup

in Windows 10 Software and Apps

DISM error 267 when trying to add drivers to WinPE setup: Hello, I’m trying create a new image and I’m having issues running basic DISM commands following MS documentation. This same documentation has worked before without issue. Not sure what I’m missing or doing wrong. Error 267 — «Unable to access the image. Make sure that the…
DISM error 267 when trying to add drivers to WinPE setup

in Windows 10 Drivers and Hardware

DISM error 267 when trying to add drivers to WinPE setup: Hello, I’m trying create a new image and I’m having issues running basic DISM commands following MS documentation. This same documentation has worked before without issue. Not sure what I’m missing or doing wrong. Error 267 — «Unable to access the image. Make sure that the…
DISM fails with error 112 when NTFS compression is enabled WinPE 10

in Windows 10 News

DISM fails with error 112 when NTFS compression is enabled WinPE 10: [ATTACH]In today’s post, we will attempt to resolve the issue of NTFS compression in WinPE 10 using all available disk space on your Windows computer. […]

This post DISM fails with error 112 when NTFS compression is enabled WinPE 10 is from TheWindowsClub.com.

read more…
Received an error when trying to run DISM

in Windows 10 BSOD Crashes and Debugging

Received an error when trying to run DISM: My laptop had problems after I accidentally turned the power off without the battery. And found about 50+ corrupted system files by doing «sfc /scannow» in safe mode.

I’m currently able to boot into the normal Windows but some functions are still not working, I tried to run…
Trying to follow @NavyLCDR directions to setup a WinPE/Win 10 Install

in Windows 10 Software and Apps

Trying to follow @NavyLCDR directions to setup a WinPE/Win 10 Install: NavyLCDR said:
[img]

I created a 6 GB FAT32 partition at the end of my second HDD. I mounted a Windows 10 installation ISO file and then copied all the files and folders from the mounted ISO file to the 6 GB partition. Then I mounted Kyhi’s Recovery Tools ISO file and…
AOMEI Backup Winpe Add extra drivers to disk

in Windows 10 Backup and Restore

AOMEI Backup Winpe Add extra drivers to disk: Hi there

Any of you using WINPE version of the AOMEI Free backup (create directly from W10) and you find you are missing drivers for example Wireless. I created my boot USB on a W10 desktop with no Wireless card.

Anyway here’s how to do it. I can’t do it on the laptop…

Источник

Why Did You Receive DISM Error 267 “Cannot Access The Image”?

In the next step, I describe how to resolve DISM error 267.

Perform Pre-Task Requirements

Retrieve The Windows Image Index

Mount The Windows Image And Then Run DISM /Image Again

Frequently Asked Questions:

My Last Words:

Windows 10: DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup — Similar Threads — DISM error 267

DISM error 0x800f080a, trying to update manually .cab add package

DISM error 0x800f080a, trying to update manually .cab add package

DISM error 0x800f080a, trying to update manually .cab add package

DISM error 267 when trying to add drivers to WinPE setup

DISM error 267 when trying to add drivers to WinPE setup

DISM fails with error 112 when NTFS compression is enabled WinPE 10

Received an error when trying to run DISM

Trying to follow @NavyLCDR directions to setup a WinPE/Win 10 Install

AOMEI Backup Winpe Add extra drivers to disk