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(160, 15%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hi , I had a working FSLogix environment on Windows 2022 and was working happily till the other day.
Now when the user logs in the profile is blank even though they have an existing VHD and FSLogix appears to see it fine. The profile upon logoff is also not saved. When the user is logged in a metadata file extension is present and removed when the user logs off.
A local profile user account is also created when the user logs in both with their name and local_username - both of these are cleared on logoff.
Deleting the original VHD gets another blank VHD profile created but once again settings aren't saved upon logoff. Verified permissions to the VHD location - user can see and access VHD location
In the logs I don't see any errors apart from these :
[09:35:35.890][tid:00000ce0.00001798][ERROR:00000002] Rename of new export (The system cannot find the file specified.)
[09:35:35.890][tid:00000ce0.00001798][ERROR:00000002] Error exporting profile registry information (The system cannot find the file specified.)
As mentioned this was previously working and I'm not sure what if anything has changed. Oddly enough I had the same issue last year in a similar environment logged it with Microsoft and didn't get any result and decided to just rebuild the environment which is the one I was using up until now.
FSLogix is updated to the latest version : 2.9.8228.50276
In the FSLogix apps operational profile log this is logged when the user logs in - though it's not flagged as an error
Profile load: Status: 100 Reason: 0 Error: 0
I've cleared the logs previoulsy but I don't think the status was 100 originally.
The same errors listed above are also logged in the ops log. Admin log is clear.
Has anyone else seen this issue ?
I've setup another two servers with the same policies and configuration as the last and they are now working as expected. Previous profiles that had data in them didn't restore the old profiles data but when logging in and modifying a file on the desktop the changes were saved as opposed to what happened before when the profile was just erased and changes were not saved. Restoring any profiles from before the issue occurred and logging back in restored the user data and logging out and in saved changes as expected. I’m still nowhere near understanding why this occurred especially considering that nothing had changed and rebuilding the environment once again solved the issue. Obviously this is not an ideal situation as I’m now under the impression that somewhere down the track I’m going to have the exact same situation occur again. If anyone does see this post and can relate please let me know I’m not alone and let me know if you have found a solution.
Well not suprisingly this has occured once more with the two newer servers and at what I thing is around the same time - exactly the same error messages and symptoms. I've rebuilt those two and as expected the FSlogix profile attachment works as expected. What I did notice is that something happens with the profile disk once it's been affected by this issue as there is data in the disk which you can't see.
Logging into the bad server with a known good profile results in a blank profile being displayed for the user and as above no changes to the profile are saved. Directing this profile once more to a good server shows a blank profile as well but on the good servers the changes are saved. Interesingly if you copy the profile from a backup before it's hit the bad server and login to the good server again the profile data ( I.e previously saved icons / files etc ) are present and changes then sync as usual - seems like the act of logging into the bad server corrupts the profile somehow.
I thought that maybe this was due to the profile data being on a file server cluster and it failing over but I reproduced that in test and couldn't get it to kill the new servers - My only other thought was that the server is running crowdstrike and the FSLogix service did appear in a detection - I've setup an exclusion for this now just in case.
This may well happen again and I still don't have a clear understanding as to why it occurs in the first place ! If anyone can help diagnose further I'd be happy to get more info. I have two good servers and one bad so I can compare logs etc.
This has occurred again - very frustrating - can I ask for some help and suggestions ?
![](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(102.4, 37%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECA%3C/text%3E%3C/svg%3E)
This happen also to our customer that use FSLogix with Citrix (without Profile Manager).
I have done a lot of tries without success.....
In the event viewer under fslogix operational i have these events
Event ID: 26 Message: Profile data export failure
Event ID: 26 Message: Export registry failure
Yes I see three of these when users login, they are in order and all errors :
Event ID: 26 Message: Rename of new export
Event ID: 26 Message: Rename of new export (The system cannot find the file specified.)
Event ID: 26 Message: Error exporting profile registry information (The system cannot find the file specified.)
I believe I have found a solution to this particular issue - it is unique to our environment hence why there hasn't been any activity around it in any forums but in case anyone else comes across this thread the solution is quite simple in the end.
In our environment we have a few processes blackholed via group policy into svchost as a way to eliminate execution - this policy includes reg.exe.
The key is located below:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\reg.exe
FSlogix must use Reg.exe during it's process somewhere - by blackholing this service we receive the error about the rename of new export which in turn affects the users existing profile. The profile resorts back to a blank empty profile and any changes are not saved.
This has been difficult for us to determine as only a subset of users have this blackholing in place - once one of them log in the symptoms begin so it appears intermittent.
By removing the blackholing on this file to SVChost the FSLogix profile handling occurs as normal - however if the profile was logged into with reg.exe blackholed then that profile is damaged - restoring to an earlier date before logging in restores the users profile.