This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 17%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi all!
While reviewing the FSLogix logs, it has been observed that most user profiles (disks) are not compacted during sign-off. The logs do not provide useful information, such as error details and codes (see the screenshot).
Previously, the compaction process was functioning correctly, allowing users to shrink their profile sizes until the FSLogix profile cache was deleted on all servers due to growth in the C drive.
A chkdsk command was run in the command prompt, but it did not find any errors.
The query is: does clearing the FSLogix profile cache lead to the issues experienced with disk compaction?
Please share your input for my query and the mystery regarding the disk compaction issue!
FSLogix version: 2.9.8884.27471
User profile type: VHDX
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 38%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi Azim ,
Thank you for reaching out to Microsoft Q&A forum.
Clearing the FSLogix profile cache does not inherently disable disk compaction. However, it can impact the effectiveness of the disk compaction process during user sign-out.
The log "Cannot shrink a partition containing a volume with errors," suggests that as there may be issues with the integrity of the VHDX file or its contents.
When the FSLogix cache is cleared while users are still logged in, uncommitted data may remain in the VHDX files. This inconsistency can lead to corrupted data in the profiles.
Cache deletion may leave behind residual or fragmented data within the VHDX file, reduces available whitespace necessary for compaction. If insufficient whitespace is detected after clearing caches, disk compaction will fail.
Clearing the FSLogix cache without implementing proper settings can lead to volume errors, insufficient whitespace, and fragmentation, ultimately impacting disk compaction processes.
Please find below documentation for more information;
https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles
https://learn.microsoft.com/en-us/fslogix/concepts-vhd-disk-compaction
If the information is helpful, please "Upvote"
If you have any queries, please let us know.
Hi @Markapuram Arun Teja Reddy
Thanks for sharing! We've implemented most of the suggestions, except for setting the defragsvc service to Automatic. For some reason, I couldn't enable it through PowerShell as an administrator, but it worked fine when configured via services.msc. I’ll continue monitoring the FSLogix logs to check for any improvements.
Hi Azim ,
Thanks for letting me know.
If you have any queries, please reach out to us. We will help you.
Hi Azim ,
I hope the information is useful.
If you have any queries, please reach out to us. We will help you.
Hi @Markapuram Arun Teja Reddy
My apologies for the delayed update. Unfortunately, setting the defragsvc service to Automatic did not resolve the issue. I also tried other approaches, such as setting both the defragsvc and smphost services to Manual, but these changes did not provide any improvement.
Running the FSLogix support tool did not provide any useful logs, as the information captured mirrored the standard FSLogix logs.
One query I have is that, this doesn’t seem to be an issue with the AVD VM itself. Could it possibly be related to user profiles? If so, how can I retrieve the relevant logs for further analysis?
Below is the article I referred to during my initial troubleshooting
https://learn.microsoft.com/en-us/fslogix/troubleshooting-vhd-disk-compaction
Hi Azim ,
Thank you for the information.
When a Fslogix clear cache is performed on a user profiles which can lead to incomplete writes or data loss in the VHDX files, which are critical for storing user profile data. If the users were active using their profiles during this cache clearance, changes made to their profiles may not be properly saved or may be corrupted. The inability of FSLogix to read these properties correctly can lead to errors during operations such as disk compaction, as you mentioned in the initial screenshot showing MaxSupportedSize: 0 and MinSupportedSize: 0.
Use chkdsk on the mounted VHDX file to check for any corruption or file system errors:
chkdsk /f "C:\Path\To\Your\VHDX.vhdx"
FSLogix also generates Event Trace Logs (ETL) that can provide detailed diagnostic information.
C:\ProgramData\FSLogix\Logs\
as these ETL files are named trace.etl.001 and trace.etl.002. However, these files are primarily intended for Microsoft internal use. To open and analyse these files you can use Windows Performance Analyzer (WPA) or Microsoft Message Analyzer tools.
If you have any queries, please let us know, we will help you.
Hi Azim ,
Just wanted to check if you have reviewed my response.
If the information is helpful, please click on "Upvote"
If you have any queries, please let me know, We will help you.
Hi Azim ,
Just wanted to check if you had got a chance to reviewe my response.
If the information is helpful, please click on "Upvote"
If you have any queries, please let me know, We will help you.
Thanks for your suggestion. However, the logs received from WFA were identical to the FSLogix logs and did not provide meaningful insights into errors related to user profiles.
We also ran the chkdsk command on the affected VHDX file, but interestingly, it reported no issues with the targeted file.
Given that previous troubleshooting attempts haven't yielded any useful results, we’ll likely wait for the upcoming FSLogix update and hope it resolves the issue.
Hi Azim ,
Just wanted to check about the latest FSLogix update to know more about regarding if any errors. If you have any other queries, please do let us know, we will help you.
Currently I dont have any other queries....will just leave the post as of now till the next fslogix update release. Appreciate the help from everyone so far, thanks!!
Hi Azim,
Thanks for the update. Please share here when you have updates or queries.
Hey Azim
Did you try out the following:
Can you share your FSLogix Settings?
I've referred to the article and cross-checked the registry values. As mentioned earlier, the logs don't provide any additional useful information beyond what I included in my initial query.
I do have another question: Will the FSLogix logs display different details or information if disk compaction fails because the size difference (size on disk vs. the minimum disk size queried) is less than 20%?
Please find the screenshots the FSLogix settings
The settings are fine from my point view.
Regarding Size Disk Alerts - I am not sure if FsLogix can do this on his own - we use a Third Party Tool to send Alerts when a FSLogix Disk is reaching its limits.