Jump to content


  • Posts

  • Joined

  • Last visited

About IT-user

  • Rank

Profile Information

  • Location
  1. Update: With fast start-up I managed to eliminate this problem on several computers. So if you still encounter this problem, try to turn this off.
  2. FYI: With 'Fast start-up' both enabled in windows and bios, I had this problem from time to time. Now I've disabled it and so far no boot problems. So my suggestion to others with this problem is to disable this (not sure wether it's also necessary to disable it in bios, but it doesn't hurt I think)
  3. Another update: Yesterday I've enabled 'fast start-up' on my pc, and this morning I encountered the login problem after months without it. So maybe this might something to do with it? Could others try to disable it to see whether this affects the problem?
  4. FYI: this didn't had any effect on my problem. I installed the UWP on my laptop and didn't encounter login problems whereas the PC's on which I deleted this, did suffer from the login problem afterwards. Any progress on the side of eset @Marcos?
  5. See my post from earlier today: maybe try to install the UWP app 'HP Programmable Key' and see if it's reproducable I've installed it myself and see if I'm affected by the problem myself in the coming days.
  6. I might be after something. I've noticed the following event entry for one of our users which experiences this problem: Custom component was loaded by another process (Registry Lock). Process name: C:\Windows\System32\DriverStore\FileRepository\hpqkbsoftwarecompnent.inf_amd64_02c16d71fe8a4b6a\HotKeyServiceUWP.exe, PID: 6464, ProfSvc PID: 1872. The registry file cannot be deleted from memory. The memory for the register is not fully available. This issue may be caused by services running as a user account. Try to configure the services to start as a LocalService or NetworkService account. (FYI: i've used google translate so this error text might not be 100% correct in English) This HotKeyServiceUWP.exe, references to the following UWP app: HP Programmable Key Within the services of the pc, I've noticed the following service which was set to autostart: HP Hotkey UWP¨service. I've disabled this service (the removal of this UWP app will probably do the same) and now I'm waiing to see if this proble does happen again. I'm not 100% sure whether this will finally resolve the problem, but it might be a good try as most of us who are experiencing this problem are using HP laptops so probably this UWP app will also be installed on them.
  7. @Marcos Today one of our users complained she had the same problem even after updating to configuration module 2099.8
  8. OK I've switched to pre-release channel for the affected machines. They now have Endpoint security 11.0.2032.0 & Configuration module 2099.8 I'll keep you updated when the problem occurs again
  9. Hello, Here is also some relevant info about our environment: HP laptops (mixture probooks + Elitebooks) with Windows 11 pro with bitlocker enabled NOT domain/AD joined - no microsoft account Eset products: Endpoint security 10.1.2058.0 Configuration module 2099.7 Detection Engine 28539 The problem is less present since I've started this topic (early November) but it still persists for some users. Let me know if you need more information.
  10. If you've switched to the prerelease channel, could you easily switch back to normal channel? I don't want my clients to run sort of beta-software. Only to solve this annoying problem, I think it would be helpful to go to pre-release channel. Link to KB article on how to change update channel.
  11. @Kurt234 Good advice, I'll also let our users know to first make a cup of coffee 😊. No, it's really helpful I'll try it the next time. It's better than rebooting & praying that the own user profile is loaded.
  12. @Kurt234 Could you explain a bit more? How long does he wait (e.g. 1 minute or until something appears on the screen?) thx for the suggestion
  13. OK thx for the extra information. FYI: the user profile is not actually deleted. The matter is that the user profile folder is changed to c:\users\temp instead of its own personal folder. The same problem as described in this link (when the problem occurs, applying the regfix solves the problem but of course this is not a long term solution).
  14. The same within our company: one user with configuration module 2099.6 still receives the same error (The user profile service service failed the sign-in. User profile cannot be loaded) from time to time. @Marcos what is the status of this issue?
  15. Thanks for your reply. I notice that I'm still on an older version for the configuration module: IThe new update will probably take some time to reach our environment I guess. However, we haven't encountered this temp profile problem for over a week now (knock wood).
  • Create New...