What you are trying to archive is against the mere concept of PCs. On a PC the owner is King, and there is no way to protect your processes from the admin.
You should go a different route, rather disabling the files until the user entered a password, just enable these files when the user has entered a password. Because this is possible.
Here are three possibilities by using encryption:
1. Encrypted Archive
Simple, have an encrypted archive (tar, zip, whatever) in which your files are stored. On password entry, decrypt these files and put them into the directory. Then use them like normal. As soon as your program that uses them is closed/the user logged out, archive these files again (you can also do it in regular intervals to be more robust against force shutdowns). Even if you don't delete these files, and they get edited, you will have the originals in the archive, and when your program starts, the corrupted files will be replaced by the archived files.
2. Virtual Drive
Take a look at for example veracrypt. This program allows you to create encrypted files that represent filesystems. When you start veracrypt you can encrypt them and veracrypt creates a virtual drive, through which you can access these files. The unencrypted files will never touch the harddrive and as soon as the veracrypt process is killed, the virtual drive, and all data in it, is gone, and only the encrypted veracrypt file is left on the machine.
3. Virtual process only filesystem
Emulate a (very simple) filesystem in your own program without using the OS filesystem. You can write an internal API to access the files in that (e.g. via creating your own TStream derivates for accessing the data), and this API in the backend than reads and writes the data into a single encrypted archive
Approach 1 is the easiest, but does not protect the files from being read. Approach 2 requires a lot of system API usage or to use an external program like veracrypt, but you can still use normal file access as much as you please and approach 3 requires the most work, you might need to rewrite your file accesses completely, but is better portable than approach 2