[Samba] Windows 10 temporary profile error, when domain remote profile directory exists and is empty
lists at boyandin.info
Wed Sep 25 05:13:45 UTC 2019
Thanks. Yes, those are known Windows mantras to fix the profile/registry
folder, in case either of them has consistency issues.
But I was doing that on brand-new, just installed Windows 10 computer,
that was thoroughly scanned with whatever anti-malware stuff was at hand
- before the user in question attempted to use it.
The only fix that handled the issue was the one I mentioned.
Renaming/deleting registry records and/profiles didn't work in my case.
On 24.09.2019 13:47, L.P.H. van Belle via samba wrote:
> You should check that if a user is logged and you look at the local
> Does it have a TEMP folder in it. If thats the case.
> I suggest you try this.
> Click Start ?¨ Run ?¨ Regedit
> Navigate to the following registry key
> Then find the GUID from the user that is having problem. (tip, properties,
security tab )
> Then under ProfileList navigate to binary key’s like this:
> On the right side under ProfileImagePath you'll see the profile path.
> Chose the one with the desired user and delete the long registry key like:
> You will then need to either rename (preferable), or delete the user
profile on disk under C:\Users\%username%
> And/or use :
> I have not used it myself yet, but looks ok.
>> -----Oorspronkelijk bericht-----
>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>> Konstantin Boyandin via samba
>> Verzonden: dinsdag 24 september 2019 3:03
>> Aan: samba at lists.samba.org
>> Onderwerp: [Samba] Windows 10 temporary profile error, when
>> domain remote profile directory exists and is empty
>> The below happens with Samba 4.7.* (didn't checked with other Samba 4
>> Setup: Samba 4.7.* AD, two domain controllers, 'computer A' and
>> 'computer B' are Windows 10 domain members.
>> 1. A user (login 'username') logs in into domain for the
>> first time, on
>> a 'computer A'.
>> Samba DC doesn't find existing profile directory and creates an empty
>> one on corresponding file server (or whatever is the correct term for
>> that), 'username.V6'.
>> 2. User marks its profile as Local on Windows and logs out. Nothing is
>> written to profile directory ('username.V6') on domain file server.
>> User then can log on and log off at 'computer A', no problems happen.
>> 3. Now user tries to log on to the same domain at 'computer B'.
>> Windows 10 tries to get profile from domain, gets an empty profile,
>> writes an error to event logs and creates a temporary profile.
>> Note: no inconsistencies in registry: there were no damaged/whatever
>> profile entry for 'username' on 'computer B'. No inconsistency under
>> "C:\Users" on 'computer B'.
>> 4. After I physically remove the empty domain profile directory
>> ('username.V6'), there's no problem logging in/logging out on
>> B'. The corresponding 'username.V6' is successfully
>> re-created on domain
>> file server.
>> Question: is this 'temporary profile error' a bug/feature of AD, or
>> Samba 4.7-specific bug/feature?
>> It's kind of inconvenient to remove empty profile each time a user
>> wishes to log on to a new domain member.
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
More information about the samba