NtfsDisable8dot3NameCreation does not take its effect for short path generation
-
The entry NtfsDisable8dot3NameCreation under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem is set to 0 by default. Now in one of the setups i tried to make this registry entry to 1 to disable short path generation. I did not find the short path getting disabled even after m/c reboot. This info is based on the article at http://support.microsoft.com/kb/121007. The article mentions the below NOTE: The change to the NtfsDisable8dot3NameCreation registry entry affects only files, folders, and profiles that are created after the change. Files that already exist are not affected. Based on this I deleted the file and the folder for which I want the short path generated and later repaired the installation. The problem that is coming is due to the degernation of short path the windows scheduler is not able to find the file to schedule with other command line params. Does something related to changing user profile needs to be done?
-
The entry NtfsDisable8dot3NameCreation under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem is set to 0 by default. Now in one of the setups i tried to make this registry entry to 1 to disable short path generation. I did not find the short path getting disabled even after m/c reboot. This info is based on the article at http://support.microsoft.com/kb/121007. The article mentions the below NOTE: The change to the NtfsDisable8dot3NameCreation registry entry affects only files, folders, and profiles that are created after the change. Files that already exist are not affected. Based on this I deleted the file and the folder for which I want the short path generated and later repaired the installation. The problem that is coming is due to the degernation of short path the windows scheduler is not able to find the file to schedule with other command line params. Does something related to changing user profile needs to be done?
Is there any explanation or hints here. Calling microsoft experts.