You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Nilesoft Shell for several months, and recently I've encountered a new issue that I didn't have before: I see .toc files being created all over my PC—in the Discord directory, in Windows/System32, or, for example, whenever I right-click on the taskbar and open Task Manager: two .toc files are immediately created on my desktop.
There are hundreds of legitimate .toc files on my PC, mostly in game directories using UE5, which have normal names.
But the ones I’m seeing now are hexadecimal codes, and the filenames themselves are also in hexadecimal.
I've realized that this issue occurs when I use Nilesoft Shell. I completely removed the program, being very thorough using Revo Uninstaller, and the issue stopped. Then, I reinstalled it, using the default script, and the problem immediately returned.
Do you know where this issue might be coming from?
The text was updated successfully, but these errors were encountered:
Windows 11 x64
I've been using Nilesoft Shell for several months, and recently I've encountered a new issue that I didn't have before: I see .toc files being created all over my PC—in the Discord directory, in Windows/System32, or, for example, whenever I right-click on the taskbar and open Task Manager: two .toc files are immediately created on my desktop.
There are hundreds of legitimate .toc files on my PC, mostly in game directories using UE5, which have normal names.
But the ones I’m seeing now are hexadecimal codes, and the filenames themselves are also in hexadecimal.
I've realized that this issue occurs when I use Nilesoft Shell. I completely removed the program, being very thorough using Revo Uninstaller, and the issue stopped. Then, I reinstalled it, using the default script, and the problem immediately returned.
Do you know where this issue might be coming from?
The text was updated successfully, but these errors were encountered: