Win11 : Where's my C:\ProgramData\ TPS file folder?

[RchdR]

Debugview is showing the app is using C:\ProgramData\MyApp\ folder to store the tps files in, yet the folder doesnt exist in File Explorer.

Is there some sort of folder redirection taking place that I’m not aware of?

TIA

[jslarve]

I’m not in front of my Clarion box, but perhaps it is looking for trace ini instructions?

[RchdR]

No ini to trace here sadly.

[Jane]

Does your program have a manifest (linked in or separate file)

INI files are in VirtualStore in Windows not ProgramData folder?

That’s odd. I would check the permissions on the ProgramData folder. If somehow your permission on that folder is not granted read/write, then I could see windows virtualizing the path. The only other thought I’ve had is are you running your application with any compatibly settings? Mark

[RchdR]

Yeah I saw that post and there is a c11 manifest file linked in manually cuz Im C6.

I think I’ll add some code to check the folder permissions/attributes from the app and show them in debugview.

I know when I was looking after servers, logged on user accounts could have redirected folders which originated from the server so it might be something like that.

OneDrive uses folder redirection which I cant get rid of either.

[Rick_UpperPark]

By default C:\ProgramData does not show in File Explorer even when you have “show hidden files and folders” checked.
Go to the address bar in File Explorer and just type in C:\ProgramData and press enter.

[RchdR]

It is visible in File Explorer and I can navigate to it. It looks like the lack of an updated manifest file was stopping the folder creation, and although the files were initially created in the C:\appfolder, deleting the tps files and reloading the app would cause a crash saying incorrect file versions.

Having spent some time on it, its like there was some sort of version control/versioning on the tps files when folder redirection takes place due to a lack of manifest.

Havent got to the bottom of why that is though, but creating the manifest in C11 so it creates the asInvoker, dpiAware and supportedOSand using it in C6 has worked and enhanced the window controls a bit despite still using the Microsoft.Windows.Common-Controls found in the Side By Side (SxS) folder.