This message was deleted.

i also have this query 🙂

I just used procmon this past week to figure out why shell was showing 50 plus seconds from inside control up. I seen the profile attached and compared it to the attachment in the programdata fslogix log files. Like u said begin session and check for RW and so on. There isn't really other way in my experience

The profile log looks like it will work. Is it in every version? Would someone be able to check that it's consistent in being here: C:\ProgramData\FSLogix\Logs\Profile

U guys build a new monitor for CU? Lol

I'm not sure. Whatever people still use? Thanks for the notice that the log does exist for the last 4 releases though.

I believe now the new version is following the standard Windows naming scheme of the year it's released with the month appended to it as well. The other version or a traditional naming scheme of 2.1 2.5 2.9 , 2.9.7 example. I'm on the second to latest version and I can confirm that the log files are in the same location. With him n program files \ fslogix they have a tool that's provides a better reading format as well. This is something you may already know https://docs.microsoft.com/en-us/fslogix/logging-diagnostics-reference

thanks!

Anytime. It's the least I could do as many times as you guys help me out with control up