Windows 10: Win10 Roaming profile .v6 folder is NOT creating in File shareDFS path

Hi MS,We have Client OS environment with Win7 and users were using roaming profiles without any issues. The .V2 folders are getting creating in the DFS share path. Since the begining of 2021, we have deployed fresh Win10 machines and users started migrating to Win10. In the initial days, the roaming profile folders .V6 were created and there was NO data loss.However, in the recent past i.e. Feb2021, the .V6 RP folders are not getting creating for the Existing and new users as well.Following testing has been done, however, the .V6 RP folders are not creating yet.1. Created a new .V6 RP profiles

:)

 

Windows 10 roaming profile includes AppData\Local & LocalNow folders

Existing Windows 7 & Windows 8.1 domain environment with accounts configured to use roaming profiles stored on a Windows 2012 server using DFS file share.

New Windows 10 Pro built for testing and logged on with an existing domain account. First hint something was wrong was the "Roaming profile not fully synchronised" errors. Looking the event log reveals lots of access denied errors from the user profile service
attempting to copy to/from AppData\Local and AppData\LocalNow.

Looking in the new v5 profile sub-folder created automatically, there is indeed three sub-folders:

• Roaming - expected
• Local - shouldn't be there
• LocalNow - shouldn't be there

The Local & LocalNow folders are not in the v2 profile from the existing Windows 7 & 8.1 clients.

Aside from these access denied errors and pop-up warning, including Local & LocalNow in the roaming profile is a really bad idea as it really slows down the log on & off process as they tend to contain large number of large files, e.g. cached application
data. The whole idea of splitting Local & LocalNow out is so this temporary/rebuildable data can be kept out of the profile.

Any idea why this is happening?

Thanks, Rob.

 

Cannot 'add folder' to Backup, error code 0x80070032 (Win10)

Hi,

Is the external drive a NTFS format?



The custom library files that are stored in your user profile will not be backed up.

Try the following suggestions and check.

• Move the library folder from the user profile path to a location outside the user profile path. For example, move the folder to the C:\MyLibraries folder.
• Exclude the library from the list of files that Windows Backup backs up. Then, include the original location of the content in the library in the backup list.
• Move the library folder to a location other than the user profile folder. Then, add a link to the moved folder from the library. Make sure that the library is included in the backup.
  

Hope this helps.

 

Windows 10 roaming profile error

New Windows 10 client that has existing windows 7 roaming profile.

Windows 10 has created .V5 profile folder but fails to create username folder in users folder on local drive, giving the using temp profile error message.

Given domain user admin permissions on Win10 machine but still no joy, an ideas what to do next?