![]() Normally the process is cached by the AppX Deployment Service. So, basically, reinstalling them each time a user signs in to their desktop. You see, the FSLogix container, and others like it, seem to insist on re-enumerating the AppX installations. It is more of why it might be slowing you down, especially with FSLogix in the mix. App Readiness Serviceīut this post is not about why you should have the service enabled. The App Readiness serviceĪs I said, this service is important, and without it, Windows Update will not work properly, your AppX packages will start to vanish, and rot will set into the deepest corners of Windows. Q: How do you know it is the App Readiness service?Ī: I used the awesome ProcMon: Process Monitor – Windows SysinternalsĪnyway, the App Readiness service is required for any modern desktop or multi-session host, so please don’t just take for granted that you can disable this service, and all your problems disappear (even though it might seem so). ![]() It is not even isolated to Windows servers because the culprit is actually the App Readiness Service, which is responsible for initializing the user profile with, among other things, AppX packages. The internet is overflowing with issues surrounding this phenomenon in both persistent and non-persistent VDI/RDS environments. And since solutions were nowhere to be found, I decided that sharing the cause and resolution with you good folks reading this blog was my duty to the community. This is what I had to deal with recently. And all they have to look at is a black screen with a cursor, no progress indicators add to that, once the desktop finally renders, the CPU is tied up for several minutes! This black screen during sign-in is NOT the best way to start your users day. Now, imagine that all your users have to wait several minutes the first time and perhaps each subsequent login. Imagine running a large RDSH farm, either on-prem or using Azure Virtual Desktop (formerly Windows Virtual Desktop). If you missed the previous post that this one extends, then do yourself a solid, and check it out in case you are going mad googling through all sorts of solutions: FSLogix slow sign-in (fix) The problem Most of the time, it might not even be FSLogix that’s at fault – or at least not entirely, which you can read about in this post where we must once again fix the OS and not FSLogix (*Psst* it’s all about App Readiness this time). Debugging FSLogix slow sign-in issues can be a stern reminder of just how many things interact with each other during the Windows login sequence.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |