Hello,
Check if the below workarounds help.
Disable Data Deduplication Service:
You can use the Disable-DedupVolume PowerShell cmdlet to disable further data deduplication activity on one or more volumes. This will not remove the existing deduplicated data, but it will stop the server from running further data deduplication jobs, and new data will not be deduplicated. However, this might not immediately make the files visible as the deduplication metadata remains intact. To undo data deduplication on a volume, you should use the Start-DedupJob cmdlet with the Unoptimization type parameter. After disabling data deduplication, you can still perform read-only deduplication cmdlet operations on the volume, but you won't be able to use job-related cmdlets or the Update-DedupStatus cmdlet for operations on the volume.
Start a Deduplication Job:
The Start-DedupJob cmdlet can be used to manually start a data deduplication job for one or more volumes. You can specify the type of job, such as Optimization, GarbageCollection, Scrubbing, or Unoptimization. This cmdlet allows you to control the deduplication process, including the amount of memory and CPU cores the job can use. For example, to start an unoptimization job on a volume, you would use a command like the following:
Start-DedupJob -Type Unoptimization -Volume "D:"
This command initiates an unoptimization job on the D: volume, which will revert the data back to its pre-deduplication state. Please note that this process may require a significant amount of storage space and time to complete.
If the Answer is helpful, please click "Accept Answer" and upvote it.