Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 2, 2020 4:12 AM | 1 vote
New Release: FSLogix Apps release 2004 (2.9.7349.30108)
This is a GENERAL release
Applies to: All supported Windows OS versions (Windows 7 and later, Server and Client 32 and 64 bit)
Download Link:
Resources:
FSLogix documentation: https://aka.ms/fslogix
FSLogix MSDN Forum: https://social.msdn.microsoft.com/Forums/en-us/home?forum=FSLogix
Open a support ticket: https://social.msdn.microsoft.com/Forums/en-US/14ea5f6f-760b-4ad2-83cf-23c3cbc1bcc4/how-to-open-an-fslogix-support-request?forum=FSLogixindex.php/knowledge-base
Request an enhancement: https://windowsvirtualdesktop.uservoice.com/forums/921289-fslogix
Installation notes:
Will upgrade over any previous release.
Changes:
- OneDrive File Icon may not be updated in certain circumstances, as an example, a file icon may not change from 'in process' to 'cloud'. This issue is RESOLVED. Internal ID# 20804166
- CheckLocationsForCreate setting has been deprecated. Internal ID# 23030228
- Cloud Cache significant performance degradation in multi-session environments during login. This issue is related to certain scenarios where single-threading would impact logins. This issue is RESOLVED. Internal ID# 23250997
- FRX Tray Tool does not support environment variables in the log path. This item is RESOLVED. Internal ID# 23427788
- Cloud Cache, in rare circumstances results in a deadlock with cldflt. This issue is RESOLVED. Internal ID# 23568222.
- FRX Tray Tool would occasionaly show 'Unknown status'. This issue is RESOLVED. Internal ID# 23594265.
- Search may re-index, when not needed, when using Skype and Outlook on the same system with Search enabled in FSLogix. This issue is RESOLVED. Internal ID# 23705869
- FSLogix Profile Container, on very rare occasions could create a deadlock in conjunction with DirNotify. This issue is RESOLVED. Internal ID# 23753376, 24397178.
- Cloud Cache provider lock file may become corrupt under certain circumstances. This item is RESOLVED. Internal ID# 23895669
- FSLogix Profile Container frxsvc Thread Crash could occur on a Windows 8.1 environment in specific scenarios. This issue is RESOLVED. Internal ID# 24102925
- FSLogix Apps (Profile Container or AppMasking) applications may not run if the associated application folders utilize a reparse point with a trailing '\ in the folder path. This scenario is almost exclusively experienced in conjunction with AppV applications. This issue is RESOLVED. Internal ID# 24367762, 162876276
- FSLogix Profile Container blue screen issue in rare cases. This issue is RESOLVED. Internal ID# 162487865, 24427979.
- FSLogix Profile Container, in rare cases, may have corrupt profile containers, including in some cases with AppV. This issue is RESOLVED. Internal ID 24447257.
- FSLogix Profile Container has rare blue screen in frxdrvvt.sys. This issue is RESOLVED. Internal ID# 165081426, 24587348.
- FSLogix Profile Container has filesystem crash. This issue is RESOLVED. Internal ID# 24909169.
- FSLogix Profile Containers now prevents user multiple user login in multiple user session environments (e.g. Windows Server) if user is configured to use FSLogix, but FSLogix is not configured for multi-session. This is NEW BEHAVIOR as these logins have been allowed in previous versions Internal ID# 25377301.
- Cloud Cache configuration options extended to allow logins and logoffs to proceed, based on administrative settings, and with implications. This functionality is documented here (https://docs.microsoft.com/fslogix/cloud-cache-configuration-reference#cloud-cache-disk-registration-settings-overview). This is an ENHANCEMENT. Internal ID# 21158311, 22981317.
All replies (25)
Friday, April 3, 2020 12:45 PM
Hi when is the release date?
Wednesday, April 15, 2020 3:42 PM
Hi,
Rumor has it that this release contains the fix for the "GPO User Policy not applied when using FSLogix profile container used" problem. However, I don't see this problem mentioned in the changes/release notes.
Best regards,
Dennis.
Wednesday, April 15, 2020 4:36 PM
See here - https://social.msdn.microsoft.com/Forums/en-US/14bed90e-67a2-4100-a282-6c7b57b68fc9/gpo-user-policy-not-applied-when-using-fslogix-profile-container-used?forum=FSLogix
Thursday, April 16, 2020 5:42 AM | 1 vote
Does anyone have details on this line.
FSLogix Profile Container has filesystem crash. This issue is RESOLVED. Internal ID# 24909169.
This appears to be what I have been trying to fix for days.
Thursday, April 16, 2020 11:04 PM
Still waiting on a download. I've requested it 3 times now and nothing.
Wednesday, April 22, 2020 8:10 PM
This fixed my server crashing issues
Thursday, April 30, 2020 12:28 AM
Did you get the link for the download? It's been 24 hours for me and I was told by today I should get it.
Thursday, April 30, 2020 12:29 AM
My servers crash every other day. Seems to be the frxdrvvt.sys file causing it. I'd really like access to test this. I've signed up already but I have not received anything yet.
Thursday, April 30, 2020 1:13 PM
Hi, did you get the download Link ? Please share it if possible.
B.R
Thursday, April 30, 2020 8:42 PM
I have put in a request over a week ago and I still have not received any link promised by the form.
Has anyone got a link they can send me please.
Thursday, April 30, 2020 10:02 PM
These notes have been updated to reflect that the bits described here are now GA.
Friday, May 1, 2020 7:57 AM
Hi,
No correction about Windows Search support on Windows 2019 with Office 2019 ?
I am still use a workaround to restart the wsearch service when the user log off but it's not an ideal solution for servers in production.
Is there another way to get it works ?
Regards
Julien
Friday, May 1, 2020 4:28 PM
Hi Julien,
The search issue is not an FSLogix issue, it's a Windows issue. I have not experienced it myself, but I have heard that Windows 10 Multi-User is also suffering from this issue. I can produce the issue with local profiles with no FSLogix and Citrix Profile Management as well. Furthermore, MS is no longer recommending to use FSLogix to roam the Windows Search Index as per these articles:
[https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht
](https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht)/en-us/fslogix/profile-container-configuration-reference (Go to the RoamSearch section)
Saturday, May 2, 2020 10:06 AM
Hi Kasper,
Do you know if there's a particular update required to enable the native user search roaming on W10 MU? I've been reading the update notes but I can't see that change listed so far.
Wednesday, May 6, 2020 2:35 PM
This latest version does not appear to install on Windows 7 32bit. Has anyone else had this issue. We are using it as part of our Windows 10 migration.
When you click the installer it attempts to load and a very brief message comes up about checking for updates, this then closes and nothing happens.
Thursday, May 7, 2020 7:09 AM
Our Microsoft-case about the search-problem was closed with it being corrected in the next Fslogix-release.
Monday, May 11, 2020 9:04 AM
Our Microsoft-case about the search-problem was closed with it being corrected in the next Fslogix-release.
Interesting. I will make some tests with the latest release and report back.
Considering I am able to reproduce the search roaming issue using local profiles (which technically isn't roaming) I am very curious to find out if FSlogix indeed is has fixed the issue. And if it does Microsoft is then using FSLogix to fix an issue which, from my point of view, is an issue in the server OS.
It's also interesting that this is not specifically mentioned in the release notes, but then again Microsoft is sometimes fixing and introducing things in their products which they "forget" to mention in the release notes.
Monday, May 11, 2020 9:07 AM
Hi Kasper,
Do you know if there's a particular update required to enable the native user search roaming on W10 MU? I've been reading the update notes but I can't see that change listed so far.
I don't know if MS has intensions of fixing it directly in Windows 10 MU. If MS has indeed fixed the issue in FSLogix, my guess is that they say that you have to use FSLogix to fix any potential windows search issues, and not fix it in the OS.
Tuesday, May 12, 2020 6:46 PM
Our Microsoft-case about the search-problem was closed with it being corrected in the next Fslogix-release.
I can confirm that the search issue is not resolved in the latest FSLogix version. We still have to use the "Event ID 2 work around"
James Kindon has some information on his blog:
https://jkindon.com/2020/03/15/windows-search-in-server-2019-and-multi-session-windows-10/
Wednesday, May 13, 2020 12:12 AM
My servers crash every other day. Seems to be the frxdrvvt.sys file causing it. I'd really like access to test this. I've signed up already but I have not received anything yet.
Did you solve your issue with the latest version ? I have also the same problem
Thanks
Friday, May 15, 2020 11:49 AM
We use the workaround of disabling the per user catalogue in Windows Server 2019. There are still weird glitches, but it is the best we've come up with
| Hive | HKEY_LOCAL_MACHINE |
| Key path | SOFTWARE\Microsoft\Windows Search |
| Value name | EnablePerUserCatalog |
| Value type | REG_DWORD |
| Value data | 0x0 |
Thursday, August 6, 2020 9:52 AM
We use the workaround of disabling the per user catalogue in Windows Server 2019. There are still weird glitches, but it is the best we've come up with
Hive HKEY_LOCAL_MACHINE Key path SOFTWARE\Microsoft\Windows Search Value name EnablePerUserCatalog Value type REG_DWORD Value data 0x0
And then you still use the roamsearch dword 2 regkey? Like in Server 2016?
I'm looking into 2019 I wonder what the best approach is to solve this. Just disable Windows Search for Outlook, use this 'workaround', or use the MS recommended way which is not working at all?
Thursday, September 24, 2020 6:10 AM
hello, is there a new fslogix version / update planned?
Sorry don't speak english
Saturday, September 26, 2020 9:57 AM
I confirm that the problem is still present in this version
Monday, October 12, 2020 8:14 AM
I confirm that the problem is still present in this version
Yup, we use the per user catalog with the scheduled task 'hack' which restarts the search service upon the event. I had to add another scheduled task to forcefully kill the searchindexer.exe process, because sometimes it hung and the entire server got stuck, people couldn't even log off.
Funny, we get all these Microsoft salesmen telling us WVD with FSLogix is the new future but FSLogix is just dead right now. Nothing is happening, no updates no fixes only more issues.
Damn shame, I would rather pay for it and get good support.