Sorry, Rob. have been busy and did not see your reply.
Since I last reported that the Recent Aplications had been removed and I sent the NPRs, I've had to restore the Recent Applications once more. I checked the Chrome version, and it has indeed been updated to Version 105.0.5195.127.
It may be possible that the Chrome Update is the cause of the problem... but then why is it only happeneing on my desktop and not on my Laptop, which was also updated to the same Version, and opens with the Recent Applications displayed?
The Chrome update is not causing the problem all the time as I haven't seen it (nor have we had others report it) on every update. Could you have some setting somewhere that is causing the profile to be modified on updates? I don't know of such a thing, but it might exist given that there are a ton of settings and management options in the browser and OS.
All I really know is the files that were there in the Chrome profile are gone which is why they have to be recreated. Nomad won't remove those files unless you use the menu option to "Reset Nomad" which I assume you aren't doing, so something is removing the files outside of Nomad's control. Browser update? Browser profile switching/corruption? OS temp cleaning? Browser configuration/settings? I don't really know - all I know is that the files were there and then they aren't and Nomad hasn't removed them so something else has. What the something else is I can't tell - just that it is happening.
You're right, there are a ton of settings in the Browser and OS... like finding a needle in a hay stack.
I have not exercised the "Reset Nomad" option.
Thx for your efforts on this Rob... is there an escalation procedure for this kind of issue?
The only "escalation" is to open a formal HCL support ticket for the issue. However, that gets to the same people that monitor this forum, so that isn't going to help as far as finding a resolution any faster. If we can figure out how to recreate the issue on demand or at least determine what seems to be causing it, we (or you) could open a Chromium bug report, but at this point, I don't think we know enough to open a Chromium bug that wouldn't just be closed as not reproducible/not enough information provided.