Blog Post

FSLogix Blog
1 MIN READ

Announcing FSLogix 2201 hotfix 1 (2.9.8171.14983) has been released!

Gonzalo_Reyna's avatar
Gonzalo_Reyna
Icon for Microsoft rankMicrosoft
May 26, 2022
Hello FSLogix nation,
 
We got some exciting news today from Jason_Parker about the release of FSLogix 2201 hotfix 1.
Summary
This update for FSLogix 2201 includes fixes to Cloud Cache and container redirection processes. No new features are included with this update.

 

Changes
IMPORTANT
This is a **hotfix** for FSLogix 2201 (2.9.8111.53415). If you are using Cloud Cache or have experienced intermittent system crashes as a result of FSLogix, it is recommended to install this update.

 

  • Resolved an issue with Cloud Cache where disk read / write blocking could potentially create a deadlock to the disk and cause the Virtual Machine to become unresponsive.
  • Resolved an issue that would cause a Virtual Machine to crash while removing profile redirections during the sign out process.

 

File Information
Download the following package: Download FSLogix 2201 hotfix 1 (2.9.8171.14983) 
Published May 26, 2022
Version 1.0
  • florent GUILLOT's avatar
    florent GUILLOT
    Copper Contributor


    Hello, Fslogix 2201/Windows 2016


    I encounter a bug where the vhdx disk does not mount,

    in which log should I look for more details?

  • vara93's avatar
    vara93
    Iron Contributor
    • Resolved an issue that would cause a Virtual Machine to crash while removing profile redirections during the sign out process.

    Is this a fix for the local_username folder hanging problem ?

  • Hi florent GUILLOT, I am sorry for the delay. If your VHDs are not mounting, assuming that you are having problems with your profiles, you would start by looking at the c:\ProgramData\FSLogix\Logs\Profile folder. There are the Profile logs.

  • Hi vara93. No, that is a different issue. The problem related to local_ folders is related to software still using files in there and, since we are not able to delete those files, a consequence is that folder will remain there. That is the general reason and to determine who is causing the problem, requires troubleshooting on each environment. As we have mentioned before, if you want our assistance on solving that issue, please open a support ticket.