How do I get this to stop happening?

[BrokenDaily]

whenever i use ntlite on my running OS (Windows 10 Pro, 64-Bit, 22H2, Build Number 19045.7291), i get ALL of these alert popups. i have to cancel them all just to get ntlite working. none of these prompt when i use ntlite to alter a downloaded windows OS via the usual microsoft downloads (or from the fido script), but they always happen on my running OS

what options do i have (excluding all of whatever could be considered "nuclear") that would let me do away with these prompts?

screenshots are too numerous to post here, so ill attach them in a .7z file (no password)

Moderator: Edited post to include a few screenshots, to make it easier to read.

 

[kriztall]

I dont really understood or cant see from ur post when u get those prompts, those packages are protected, u would get also Access denied when u try to remove them manually.
In case u get them when u Confirm the session to proceed with removal and so on, then they shouldnt come of course, while i dont even recommend to remove those components but thats not the question.

Edit:
I see, in Updates tab they dont exist, so u get them on the removal process, then only nuhi can help
Just make sure no other App doesnt have also access to the mount folder at the same time
But a bit more information from u would not be bad, when i would get thas as a report i may need to ask several questions which i dont need to ask.

 

[tistou77]

If you have Defender, did you disable the relevant option before launching the NTLite process ?
Or could another antivirus be causing this problem

 

[BrokenDaily]

If you have Defender, did you disable the relevant option before launching the NTLite process ?
Or could another antivirus be causing this problem

sorry for the late reply, but i did. i temporarily disabled (turned off) "real-time protection", "cloud-delivered protection, "automatic sample submission", and "tamper protection". even at the time of this post, i did the same thing, and im still getting the prompts (my fingers ache, so much clicking)

 

[kriztall]

sorry for the late reply, but i did. i temporarily disabled (turned off) "real-time protection", "cloud-delivered protection, "automatic sample submission", and "tamper protection". even at the time of this post, i did the same thing, and im still getting the prompts (my fingers ache, so much clicking)

Just download the tiny portable app "opened files view" from nirsoft and u should see what App does use those files. Since i dont think its says that they are in use while they are not.
Or its a permission problem, one of this two iam pretty sure it is
Also try "FileAccessErrorView" also from nirsoft

 

[BrokenDaily]

again, sorry for the late reply, i keep getting side tracked with other IRL stuff, i'll try not to make this a habit

while i was loading up my OS in ntlite, the opened files view app showed no results, but the FileAccessErrorView app gave plenty

 

[BrokenDaily]

ok, i found out something interesting. in another forum, to solve a weird permissions thing for a defunct task scheduler entry, i was told to use PowerRun (which lets one run certain programs as TrustedInstaller / Nt Authority/system), and then use task scheduler through it to delete said defunct entry. it worked. fast forward a few weeks, i suddenly had the thought to run NTlite through it, so i did, and tried loading up my OS, and i did NOT get the warning prompts. I didn't alter anything with it though, since afterwards i immediately unloaded the OS and shut ntlite down, so nothing was changed, but now i know there's something weird going on with file permissions, and PowerRun can help bypass those, so.......yeah :/

 

[Anonymous Internet User]

PowerRun is a known and very useful tool that many here use for various purposes (like replacing or editing certain protected Windows files, such as imageres.dll.mun for example), but you should not not need it to run NTLite. You're either doing something wrong or you have some third party security software or there is something wrong with your PC/Windows. I've done Win 10 and 11 builds recently and many in the past and I have never seen such errors when running NTLite.

This is not a problem with NTLite, but with your setup.

 

[16309]

PowerRun is now at v1.9

 

[BrokenDaily]

PowerRun is a known and very useful tool that many here use for various purposes (like replacing or editing certain protected Windows files, such as imageres.dll.mun for example), but you should not not need it to run NTLite. You're either doing something wrong or you have some third party security software or there is something wrong with your PC/Windows. I've done Win 10 and 11 builds recently and many in the past and I have never seen such errors when running NTLite.

This is not a problem with NTLite, but with your setup.

well a while back (think a year or so), to solve what was a bit of a snafu i might've encountered, i made sure to grab a fresh 22H2 iso via the fido script, all the non-esu updates and smaller bits, and the appx/msixbundle/appxbundle files to the windows store app (along with the dependencies) via this link (making sure to get the product IDs long beforehand, and making sure the dropdown "Ring" menu was set to retail[default os]), and used NTLite to create a non-esu updated win10 22H2 install, of which i ran for a repair install. At that point, it was technically downgraded to a non-esu setup, but after i then downloaded the ESU update via NTLite, and ran it, my computer was now re-registered back onto the ESU update path, and it was fully update back to what it was before, minus the jank.

had to reconfigure some stuff after that, but then it was all fine. maybe i installed some dependencies i didn't really need to? but even if i wanted to uninstall the unnecessary dependencies, i wouldn't know where to start. unless i could get help on that front somehow?

regardless, running NTLite through the PowerRun app bypasses the warnings, and lets me get things done quicker, so that's a plus alsoi i updated my PowerRun app. side note: would i need to replace the .ini config file as well during the "update", or is it samey enough that i don't need to? because i had to re-add some entries after the fact

 

[Anonymous Internet User]

regardless, running NTLite through the PowerRun app bypasses the warnings, and lets me get things done quicker

Yes, but that's a sign of something being wrong. This isn't normal. Extra dependencies just sitting around on disk won't cause such problems. This looks more like permissions issue or maybe a damaged file or something else is locking the file for some reason. Perhaps reinstalling DonNET packages might be worth trying?

You shouldn't just accept this as status quo: "oh well, it works now". There is some underlying issue on that PC that should be looked into because you don't know what else may be affected.

Since PowerRun is distributed with an .ini file I tend to replace mine with the new one, but I haven't really added anything to it so I never gave it much thought.

 

[BrokenDaily]

i imagine you meant "DotNET" packages, and since idk what those would be shown as in "Programs and Files"/"Revo Uninstaller Pro", i took two screenshots of what would probably be what you're talking about? (ignore the red x, that's microsoft edge)

this is what i got for the 1st (the numerous C++ runtimes were from here), and the 2nd one is the times i went to use certain desktop programs, but for some reason, they would only run while specific ".NET Desktop Runtime" versions were installed (I kept said installation files, so reinstalls can be done if needed)

if any of this relates to whatever i need to reinstall (or run a repair via "Programs and Files"), then i'd appreciate the help, otherwise if the DotNET packages are something separate & downloadable, i'd greatly appreciate a link pls, because i don't really know if doing another repair install of windows 10 would "fix" anything, since i did that already, and.....it did nothin (also i'd have to reinstall the ESU upgrades after technically downgrading via the repair install, and....i'd rather not if i don't have to)

Edit#1: i "repair/reinstalled" the 4.7.2 targeting pack, and the (enu) pack, the two .net runtimes, and the asp.net core, and tried running ntlite normally. still getting the prompts. is there some powershell commands i could run to maybe fix the issue, or uninstall the errant things?

 

[BrokenDaily]

wait, hold on, idk if this might be relevant, but on a whim, i loaded up ntlite via PowerRun, loaded windows, and i went to "components > API & Runtime", scrolled down, and saw this


now, i haven't touched this at all, and have left it alone, but if any of this seems like the problem, what would i do next? (excluding the data access components entry)