We traced the issue to the use of WatchGuard EPDR on this server.
WatchGuard issued a hotfix as a result of opening a case - this resolved the issue.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a recent issue - since the 2024-06 CU for server2016.
My client has a number of shared Excel files on the network share. Most of these when opened create a temporary file prefixed with a ~ that is removed when closed.
The shared Excel files appear to generate a file with a random 8 character .tmp file (78F9A289.tmp for example) that are not deleted.
These files have a blank "You must have read permissions..) in the security tab.
I have tried:
Taking ownership - denied.
Changing the parent folder permissions (inheritance) - denied
Using psexec to run cmd as the SYSTEM account to edit permissions - Denied.
The only way to remove the files is to dismount the disk momentarily - after which the permissions appear & the files can be purged.
Any ideas on the cause & resolution since these files are filling up the drive?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
We traced the issue to the use of WatchGuard EPDR on this server.
WatchGuard issued a hotfix as a result of opening a case - this resolved the issue.
Further to this - also tried Launching Excel is safe mode etc.. all resulted in a new .tmp file
Also disabled "Allow caching of share" for the parent folder.
Killed all sessions to the share to ensure no user sessions were active
Checked System>Storage - this can only see the recycle bin since the system account can't read these .tmp files util a dismount/remount is performed.
I have the same problem. After server restart i could delete de tmp files
Windows Server 2019 and Office 2016. Since June 2024
We traced the issue to the use of WatchGuard EPDR on this server.
WatchGuard issued a hotfix as a result of opening a case - this resolved the issue.
We use Watchguard edpr. I made a case to receive the hotfix
Had the same issue and WatchGuard sent a hotfix