0
1
Windows 7 (32-bit)
I have an application that requires short path syntax for a sub-directory under Program Files (c:\Program Files\Foo Example\Foo Example2).
On MOST of my user systems, it's enabled by default and working fine. However on a select sub-set of users, it's disabled (I'm not sure why since everyone uses a common image).
I've tried enabling it via fsutil 8dot3name set 0
(from command-prompt using admin privileges). That command seems to run fine (no error). But when I try actually creating the short name I get:
C:\>fsutil file setshortname "Program Files" PROGRA~1
Error: Access is denied.
Any thoughts on how to debug this and determine why Windows won't let me add this? Is there an error log I can check somewhere?
Update
As per request, here's what I see when typing DIR P* /X
C:\>DIR P* /X
Volume in drive C has no label.
Volume Serial Number is XXXX-XXXX
Directory of C:\
07/13/2009 10:20 PM <DIR> PerfLogs
03/13/2014 02:47 PM <DIR> Program Files
03/13/2014 02:48 PM <DIR> Program Files (x86)
0 File(s) 0 bytes
3 Dir(s) 412,723,027,968 bytes free
I may be off here, but would it help to use "SET" (http://ss64.com/nt/set.html)? Typing SET in cmd may show preset variables such as "ProgramFiles(x86)=C:\Program Files (x86)". In which case, you can use the variable in place of the full path. EG "echo %ProgramFiles(x86)%" will return "C:\Program Files (x86)"
– root – 2014-07-09T14:59:47.887This a internal or third-party application? Because Program Files is not the proper place to place application data hasn't been for a very long time. – Ramhound – 2014-04-25T16:01:45.007
Perhaps "PROGRA~1" already exist? Can you CD into it? – Ƭᴇcʜιᴇ007 – 2014-04-25T16:04:06.963