Local Profiles are not getting deleted after user logoff

Nadeem Hussain Joo 1 Reputation point

Hi everyone

Local profiles are not getting deleted from machines in hostpool. Instead when user log's in again, user gets one more local profile created as user1 if user is getting session from the same machine.

Again when the user logsoff and disconnects session, both local profiles stays there.

DeleteLocalProfileWhenVHDshouldApply registry is already enabled.

FSlogix Version :- 2.9.8440.42104

Appreciate your support here.



Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,189 questions
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
434 questions
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 21,461 Reputation points Microsoft Employee

    Hello Nadeem Hussain Joo

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    Based on the information you provided, it seems like the DeleteLocalProfileWhenVHDshouldApply registry key is not working as expected. This key is used to delete the local profile when the user logs off and the profile container is applied.

    To troubleshoot this issue, you can try the following steps:

    1. Check if the registry key is set correctly on the machine where the user is logging in. You can use the Registry Editor to check the registry key values.
    2. Check if the user has the necessary permissions to access the profile container. The user should have read and write permissions to the profile container.
    3. Check if the FSLogix service is running on the machine where the user is logging in. You can use the Services console to check the status of the FSLogix service.
    4. Check if there are any errors in the FSLogix logs. You can find the logs in the Event Viewer under Applications and Services Logs > FSLogix.

    Hope that helps.

    0 comments No comments