FSLogix 2105 HF_01 (2.9.7979.62170) released

Hi Mike_Zirbes , put the service to the stopped status and stop it.

For some reason, microsoft developers ignore critical problems with their product.

Anyone else seeing problems with black screen at login for 5min? All my digging has pointed to the AppReadiness service and possibly corrupted fslogix profile disk.  Event logs show an NTFS disk check running on the profile disk, which probably causes a timing issue with AppReadiness. Eventually, the desktop appears but the start menu does not work. Task manager shows a runaway Push notification that is consuming excessive RAM (20+GB and growing). Killing the runaway process allows the left click start menu to start working (eventually) but GPOs have not applied properly so users have other probelms.

The only thing I have found that seems to fix this is to delete and have a new user profile created.

It's been a year now, and Microsoft doesn't want to solve the problem. I don't know what's wrong with them.

I temporarily fixed this problem with a script in the task scheduler.

1. On each RDSH server I created a folder C:\PS and put this script there:

$Event = Get-WinEvent -MaxEvents 1 -FilterHashtable @{logname='Microsoft-FSLogix-Apps/Operational';ID='31'}

$TimeCreated = $Event.TimeCreated

$Event = [xml]$Event.ToXml() 

$User = $Event.Event.EventData.Data | Where-Object {$_.name -eq "Username"}
$SID = $Event.Event.EventData.Data | Where-Object {$_.name -eq "SID"}

$RefCount = (Get-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$($SID."#text")").RefCount[0] 

if( $RefCount -ne 0 )
{
    "$TimeCreated, $($User.""#text""), $($SID."#text"), $($env:COMPUTERNAME)" | out-file \\resoleasing.com\NETLOGON\RDS\FSLogix\FSlogix.txt -Append
    Set-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$($SID."#text")" -Name RefCount -Value ([byte[]](0x00,0x00,0x00,0x00))
}

2. In the task scheduler, I had to run the task under my account, for all users with the highest rights.

Trigger:

This event occurs when a profile is unloaded.

Programm: powershell.exe

Arguments: -NoProfile -NoLogo -NonInteractive -ExecutionPolicy Bypass -File C:\PS\FixLockoutProfile.ps1

https://docs.microsoft.com/en-us/answers/questions/229309/fslogix-unclean-logoff-causing-locked-files-until.html?page=8&pageSize=10&sort=oldest
Please take this seriously, it's been months and it's affecting all my customers productivity.

the long-pending issue of profile stuck is not been address

It would be better if you fixed the bugs...