displayed files that does not exist in Program Files(x86)??
-
Hi guys
I'm working on improving an application developed by QT , i have a problem , when i try to open files from my app ,
there are two files that do not exist in the directory but that are displayed (.ini files see the screenshot), where can they come from ? , after some research I noticed that if I create a copy of my installation files in another directory (outside ProgramFile (x86)) there are no invisible files (.ini), can the problem come from my operating system (windows 10)?
these files exist but not in the ProgramFilesx86/CkConfigManager, is it possible that windows posted them in the wrong place?
Thanks
my english is average, please use simple words and try to be the most explicit, thank you
-
Hi guys
I'm working on improving an application developed by QT , i have a problem , when i try to open files from my app ,
there are two files that do not exist in the directory but that are displayed (.ini files see the screenshot), where can they come from ? , after some research I noticed that if I create a copy of my installation files in another directory (outside ProgramFile (x86)) there are no invisible files (.ini), can the problem come from my operating system (windows 10)?
these files exist but not in the ProgramFilesx86/CkConfigManager, is it possible that windows posted them in the wrong place?
Thanks@Zunneh said in invisible files in Program Files(x86)??:
there are two files that do not exist in the directory but that are displayed (.ini files see the screenshot)
If they are displayed, they exist.
Check your code for any occurrence of QSettings - it's likely the app is creating these files, although that location is uncommon.
-
when i try to modify one of this 2 files from the QDialog , he says "impossible to modify inexsisting files , so they don't exist , why they are displayed ? i can modify program.in (it exist ) but not thoose 2 files
-
I have no idea.
-
Windows has a VirtualStore directory for files that are redirected from locations that are read only that were allowed in older versions of Windows. It sounds like this is what is happening.
Have a look under "C:\Users<your user name>\AppData\Local\VirtualStore" You will likely find the Program Files(x86) folder and the missing files.
This is more for legacy applications that tend to write data in the installation folder of the software or in other locations they shouldn't have been writing files to. You could get away with this on WinXP and down particularly if you were running with admin privileges but Vista and up redirect the files.
This 'feature' has cause many problems and lots of confusion. You end up with a file that doesn't really exist in the location you think it is (Windows will show you it exists when viewing through explorer) or worse is when you think you have modified an existing file but really didn't.
-
Windows has a VirtualStore directory for files that are redirected from locations that are read only that were allowed in older versions of Windows. It sounds like this is what is happening.
Have a look under "C:\Users<your user name>\AppData\Local\VirtualStore" You will likely find the Program Files(x86) folder and the missing files.
This is more for legacy applications that tend to write data in the installation folder of the software or in other locations they shouldn't have been writing files to. You could get away with this on WinXP and down particularly if you were running with admin privileges but Vista and up redirect the files.
This 'feature' has cause many problems and lots of confusion. You end up with a file that doesn't really exist in the location you think it is (Windows will show you it exists when viewing through explorer) or worse is when you think you have modified an existing file but really didn't.
@Rondog said in displayed files that does not exist in Program Files(x86)??:
This 'feature' has cause many problems and lots of confusion.
I couldn't agree you more! We ended installing our legacy programs in separate folders outside the program folders to workaround these workarounds. Up to now (Windows 10) it works fine. Let's see what happens with the next release ;)
