Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

NTUSER.DAT locked by process

Does PDQ Inventory ever touch ntuser.dat in a user's profile? While running 12.3 Enterprise with the default scan profile we had a bunch of machine's ntuser.dat files get locked by a process preventing their profile from loading when the users logged in. The only thing we had changed recently was adding PDQ Inventory and it's scans so my boss made me shut it down. It's been a month and we haven't seen that issue since. We weren't able to determine which process locked the files. I'm still using PDQ Deploy Enterprise though and love it. Can't wait to fire up PDQ Inventory again, especially v13 with Central Store.

Love the webcasts with Shane and Lex too. PDQ rocks!!! \m/

0

Comments

3 comments
Date Votes
  • I've never seen PDQ Inventory lock the ntuser.dat file. By default it's not scanning for it. Can you fire up ProcMon on a test machine, and PDQ Inventory and Scan that particular host? I'd be flabergasted if the inventory scan touched and locked that process. 

    My guess is something with A/V and the scan causing the file to lock. But that is grabbing at straws without seeing error output and some logs. 

    0
  • I didn't think so either. Unfortunately the users and some of our staff had already rebooted the machines to regain access to their profiles so by the time I looked at them the problem was gone and hasn't reappeared in over a month. We've never seen that issue in the past either.

    Going to fire up PDQ Inventory again next week and limit testing to IT machines at first to see if the issue appears on any of our machines, but I don't think it will. I can fire up ProcMon at that time too.

    0
  • Post back with your findings. Rather I or someone from PDQ will chime in to help. Though I may suggest emailing support at that time too, but I'll know more once I have some details.

    0