Dism error 6824: The operation cannot be performed because another transaction is depending on the fact that this property will not change.

Subscriber43 · Sep 8, 2023

I've been getting this error in the last two beta updates. I've tried a multitude of fixes, including the ones found here. Nothing has worked.
Maybe I'm doing it wrong?
Others have reported success using the same procedures outlined in this forum and elsewhere.
22631.2271 Beta.

hsehestedt · Sep 8, 2023

Subscriber43 said:
I've been getting this error in the last two beta updates. I've tried a multitude of fixes, including the ones found here. Nothing has worked.
Maybe I'm doing it wrong?
Others have reported success using the same procedures outlined in this forum and elsewhere.
22631.2271 Beta.

I suspect that I know what is causing this, but I need to get back in front of my main system to get you details.

For now, please try a different folder for your DISM operation. For example, if you created a folder called C:\project and you are using DISM to operate on files in that folder, create a whole new folder such as C:\project2, and place your files there. Try your DISM operations there. Does that work?

Also, can you tell me what it is you are doing in DISM when you get this error? Is it happening when you try to commit changes?

I'll follow up with you later, but it will be a while.

hsehestedt · Sep 8, 2023

Okay, here is my thinking on what MIGHT be happening:

If you work with DISM and an image gets left in an open state and does not close properly, it may cause the issue that you are seeing.

Start by checking to see if there are any open DISM mounts like this:

Dism /Get-MountedImageInfo

If there are run the following series of commands. Note that you may need to change the folder names to match your situation:

DISM /Unmount-Image /MountDir:"C:\Project\Mount" /Discard
DISM /Cleanup-WIM
DISM /Cleanup-Mountpoints
C:\windows\system32\takeown /f "C:\Project\*.*" /r /d y
icacls "C:\Project\*.*" /T /grant %username%:F

Now, delete the folder that held your files.
Empty the Recycle Bin.
Reboot the system.

NOTE: If you were not able to delete the folder, you may need to reboot first, then try to delete the folders.

Finally, if I was correct and this was the cause of the problem, my suggestion would be to either temporarily suspend real-time antivirus scanning or set an exception for the folder that you are working with. I see AV software causing problems with DISM all the time.

Subscriber43 · Sep 9, 2023

@hsehestedt

Thank you for the response.

This is the command that produces the error:
dism.exe /online /cleanup-Image /StartComponentCleanup /ResetBase

All other DISM commands execute properly (with no error).

hsehestedt · Sep 9, 2023

If you run this does it show any mounted images?

Dism /Get-MountedImageInfo

Subscriber43 · Sep 9, 2023

hsehestedt said:
If you run this does it show any mounted images?

Dism /Get-MountedImageInfo

No. Nothing comes up.

Spunk · Sep 9, 2023

At command prompt (x:\sources) type this exactly as written:
bcdedit |find “osdevice” (Must inc ” and the | ), the | before Find is the Upper case \ key) press enter. This will tell you what drive letter the OS is on. It may not be on the C: drive.
Now use the returned as the drive letter for OS, for this example, assume C: or whatever drive letter is the OS device.

If typing commands in, you have to change the Drive letter to the OS Drive letter before attempting.

mecanicogolf · Feb 28, 2024

Spunk said:
At command prompt (x:\sources) type this exactly as written:
bcdedit |find “osdevice” (Must inc ” and the | ), the | before Find is the Upper case \ key) press enter. This will tell you what drive letter the OS is on. It may not be on the C: drive.
Now use the returned as the drive letter for OS, for this example, assume C: or whatever drive letter is the OS device.

If typing commands in, you have to change the Drive letter to the OS Drive letter before attempting.

All above steps did not work for me. Any other suggestions? Reinstall or reset Windows?

Griff79 · Feb 28, 2024

mecanicogolf said:
All above steps did not work for me. Any other suggestions? Reinstall or reset Windows?

Having the same issue on Beta Build 22635.3212...

Attempting a repair install to see if it fixes the issue

mecanicogolf · Feb 28, 2024

Griff79 said:
Having the same issue on Beta Build 22635.3212...

Attempting a repair install to see if it fixes the issue
View attachment 88569

Me too!

garlin · Feb 29, 2024

This sounds stupid, but try restarting the system twice in a row. I think there's pending DISM operations, and they can't be cleared until a reboot. Worse case, it won't do any harm.

mecanicogolf · Feb 29, 2024

garlin said:
This sounds stupid, but try restarting the system twice in a row. I think there's pending DISM operations, and they can't be cleared until a reboot. Worse case, it won't do any harm.

I tried that. No go. And its not stupid. If something is wrong, you try and fix it. At least I do.
Why doesn't it harm anything?

mecanicogolf · Feb 29, 2024

Griff79 said:
Having the same issue on Beta Build 22635.3212...

Attempting a repair install to see if it fixes the issue
View attachment 88569

Did you fix the issue?

Bree · Feb 29, 2024

Subscriber43 said:
This is the command that produces the error:
dism.exe /online /cleanup-Image /StartComponentCleanup /ResetBase

Griff79 said:
Having the same issue on Beta Build 22635.3212...

mecanicogolf said:
Me too!

I have seen that error 6824 before, and I saw it again with 22635.3212.

The fix is to perform an offline cleanup rather than an online one. When your windows image is offline there can be no pending transactions because the OS isn't running. I last saw this bug in July last year. Fortunately I worked out how to fix it back then. Fix is here:

KB5028247 Windows 11 Insider Beta 22621.2048 and 22631.2048 - July 13 - post #22

mecanicogolf · Apr 1, 2024

Bree said:
I have seen that error 6824 before, and I saw it again with 22635.3212.

The fix is to perform an offline cleanup rather than an online one. When your windows image is offline there can be no pending transactions because the OS isn't running. I last saw this bug in July last year. Fortunately I worked out how to fix it back then. Fix is here:

KB5028247 Windows 11 Insider Beta 22621.2048 and 22631.2048 - July 13 - post #22

You say "offline". What exactly do you mean by this term. Does it mean turn off wi-fi? Do you mean Safe-Mode? Sorry, I don't have my tech dictionary handy right now. You know, the one that says "Win 11 for Dummies"

Rollback_Jockey · Apr 1, 2024

'Online' refers to the currently mounted OS

mecanicogolf · Apr 1, 2024

Rollback_Jockey said:
'Online' refers to the currently mounted OS

Great. So how do I perform this maneuver offline?

Cowboy · Apr 1, 2024

I saw that output yesterday. I went to Windows Update, and saw it was busy at the time. After completion the dism ResetBase then worked.

Bree · Apr 1, 2024

mecanicogolf said:
Great. So how do I perform this maneuver offline?

'Offline' refers to the OS you are using DISM to clean up. You don't want it running, you need to boot to a Command Prompt from something else. That could be a Windows install usb, of in this example below I used a Macrium Reflect recovery drive. You just need the OS you are cleaning up to be offline, as in you've booted from something else.

You need to boot from something else so that your Windows isn't running while you run Dism offline. If you are booting from a Windows install usb, then first create a folder on your C: drive that DISM can use for a scratch directory, eg. C:\Temp. Then boot to the Advanced Startup recovery environment and open a command prompt.

Typically the command you use will be something like:
DISM /Image:C:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
(note that your Windows drive may not be the C: drive if you have just booted from an install usb)

mecanicogolf · Apr 2, 2024

Bree said:
'Offline' refers to the OS you are using DISM to clean up. You don't want it running, you need to boot to a Command Prompt from something else. That could be a Windows install usb, of in this example below I used a Macrium Reflect recovery drive. You just need the OS you are cleaning up to be offline, as in you've booted from something else.

You need to boot from something else so that your Windows isn't running while you run Dism offline. If you are booting from a Windows install usb, then first create a folder on your C: drive that DISM can use for a scratch directory, eg. C:\Temp. Then boot to the Advanced Startup recovery environment and open a command prompt.

Typically the command you use will be something like:
DISM /Image:C:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
(note that your Windows drive may not be the C: drive if you have just booted from an install usb)