(Solved) Error 0x80070005 - Access is denied

[Tweakfiend]

Hi
I have been registered using your program for 6- 7 years and never had any error until recently.

The above error appeared first 3 0r more weeks ago only when accessing NTLite function = "updates" when trying to produce an iso backup.

Other functions and drivers / item removals etc worked at that point.

I then reinstalled Windows 11 to try again, and on reinstalling your program, it runs but ,the same error is extended to drivers ,which did not load , ,and items removed such as legacy components , directplay.

Windows Update works normally !
The Windows 11 system is initially installed from UUPDump iso and a flash drive installer , whose integrity was checked via BitDefender

I have extensively tried all internet solutions I have seen connected with 0x8007005 errors , inc "rights" attributes " sfc /scannow etc etc.

No help . I have checked anti virus setting and even disabled it.( BitDefender )
The end result is your programs processes will now not complete.

I have even tried Windows 11 memory checker.

I have a lot of different software loaded on my PC ,and this error does not show up on any other software.

New error (s) now appeared as attached

Please advise

 

[Deleted member 8142]

I don't see the connection to .NET, NTLite doesn't require it to run. Error 0x80070005 is Access denied, or DISM is messed up.
Even if you don't pre-integrate updates from the UUPdump script, an unpatched image would still load.

oops my reply was out of topic . i admit it. yes NTLite will load unpatched image flawlessly.

 

[Tweakfiend]

Tweakfiend, thanks for the report.

Tested the integration of Win11 with latest KBs, all processed fine, so we will need a bit more info to see what is going on.

Let's start with your DISM log, meaning when you get the error please attach %temp%\ntlite_dism.log, and ntlite.log while at it.

2 ideas if guessing before seeing the logs:

- in NTLite File - Settings, are temporary and scratch folders default (same as %temp% in explorer would lead to), or some custom ones?
And in both cases make sure the NTFS permissions weren't tampered with.
One of common issues is a use of RAM drive for temp/scratch dirs, sometimes it doesn't gel well with DISM.

- Any antivirus/antimalware protections in the background that could interfere during integration?
I see some shields in the tray, try suspending their protections just while debugging.

Each time when retesting, unload the image to reset it. Also recopy fresh image files if there was any saving going on before loading again.

And if in a hurry, or just interested to confirm if it's the host, try editing an image inside a normally set virtual machine.

Hi Nuhi

I have attached NTLite screen errors and logs . I loaded a new windows 11 image from Microsoft for the purpose and as b4 loaded image from
previous NTLite running was deleted.
I do not use RAM drive and BitDefender anti virus was disabled ( Had removed this previously and still had errors ) I do not change any NTLite permissions .
I only ever use default sequence of updates + drivers + unnecessary process removals + wim based iso to complete.
I originally thought that 0x80070005 errors could also be memory related, although win11 mem diag says not.
Its a mystery !

 

[garlin]

Again, I believe your host's current DISM setup is corrupted and beyond fixing (even with NTLite host reinstall). If you didn't save the original preset, then it's guesswork which Servicing Stack components got removed.

It's a chicken-and-egg problem. Without the preset, we need NTLite /forcelistcomponents to "recreate" the removals list. NTLite can't do it without a working DISM. We can't restore DISM on a live host by itself, since it would require DISM.

If you don't want to be struggling for days, reinstall Windows from the untouched ISO. To preserve your existing data, use Setup's Upgrade option to have Windows rename the old folder, and create a new Windows.

Chalk this up to a learning experience. Save your presets.

 

[Tweakfiend]

Again, I believe your host's current DISM setup is corrupted and beyond fixing (even with NTLite host reinstall). If you didn't save the original preset, then it's guesswork which Servicing Stack components got removed.

It's a chicken-and-egg problem. Without the preset, we need NTLite /forcelistcomponents to "recreate" the removals list. NTLite can't do it without a working DISM. We can't restore DISM on a live host by itself, since it would require DISM.

If you don't want to be struggling for days, reinstall Windows from the untouched ISO. To preserve your existing data, use Setup's Upgrade option to have Windows rename the old folder, and create a new Windows.

Chalk this up to a learning experience. Save your presets.

Thanks

However 1) I did process DISM repair 5 times, but never any errors showed on it, before or after fresh reinstall of Windows 11 2) I did install a newly downloaded iso from Microsoft after formatting drive 3) the fresh NT Lite presets each time resulted in processing corruptions, so why reuse them , hence saving them not considered ( ?)

 

[garlin]

Right now, we have insufficient info to retrace your steps. The screenshot shows 341 removed components, even if we assume about 200 of them are unnecessary drivers, languages or keyboards -- it leaves open the possibility DISM-related components got removed unless you can absolutely remember not touching Servicing Stack, WinSxS.

Now if we presume you have a clean Windows installed, clean download of NTLite, and no antivirus software problems -- then the only other culprit would be not having the correct Administrator rights, or wrong permissions on the ISO or NTLite temp folders. Which you can remove, and have NTLite recreate.

 

[Necrosaro]

Each ti

I deleted each preset of NTLite that resuilted in processing errors .The last attempt a few minutes ago would not load "updates" and showed multiple errors ( 0x8007005) on all entries removed , but did complete, and the resulting ISO on testing shows it should install Windows 11.

I have uploaded therefore this latest "preset" version.

Of course reinstalling NT Lite has its own problems , as only 3 installations allowed b4 emailing nuhi.

BTW I normally backup NT Lite with AOMEI backup to save this problem , as I reinstall Windows several times a year due to beta testing a lot of s/ware. This time however I did reinstall NT Lite software.

Software activation is by standard tied to a machine.
Activation is stored in a license.dat file inside the tool's installation folder, which can be backed up in case the folder is deleted.
If you don't keep the folder on some other partition, make sure to backup license.dat from it in-between OS reinstalls (File - Manage License - Export).
To activate it on more of your hardware, you as a single user, spend some of those 5 activations on those other machines - make sure to keep their license.dat file backed up as well.


Additional tips:
- you can use the same license.dat file to append multiple activations to it, to not need to save different one for each machine.
In other words keep the previous file in-place before starting the tool when activating on a new hardware to write over it, then backup the new updated file which will cover both machines.

- If the tool is ran from a different virtual machine, it will see a different machine.
It cannot pass through virtual machine and get to the host, except the CPU info.

Dino sent me this when I was reactivating after 5. Helps out a lot as a heads-up

 

[garlin]

Tweakfiend's NTLite is properly licensed, as reported by the preset.

 

[Tweakfiend]

Right now, we have insufficient info to retrace your steps. The screenshot shows 341 removed components, even if we assume about 200 of them are unnecessary drivers, languages or keyboards -- it leaves open the possibility DISM-related components got removed unless you can absolutely remember not touching Servicing Stack, WinSxS.

Now if we presume you have a clean Windows installed, clean download of NTLite, and no antivirus software problems -- then the only other culprit would be not having the correct Administrator rights, or wrong permissions on the ISO or NTLite temp folders. Which you can remove, and have NTLite recreate.

Thanks for reply
I never touch Servicing stack or WinSXS. and ISO permissions were correct . I am the only administrator.

I tried a few minutes ago to run NTLite, having first deleted NTLite Windows temp files and rechecking admin rights/ user access.

I did not tick the "DISM" box after updates were processed , but 3 of 4 updates were "skipped" as before.

Also all removal items showed "access denied" and so did not complete, apart from language / keyboard item removals !
All the main NTLite processing "headings" show green after completion, although some of the sub sections as mentioned show blue

The process however carried on as if this was normal and completed the iso at the end.!
All source drivers loaded !

 

[garlin]

Next step would be to remove NTLite's Updates folder (you can always redownload), and allow it to recreate. Same possible permission issue.
Removals sound like a TrustedInstaller issue, run a "sfc /scannow" to revert any incorrect permission changes.

 

[Tweakfiend]

Next step would be to remove NTLite's Updates folder (you can always redownload), and allow it to recreate. Same possible permission issue.
Removals sound like a TrustedInstaller issue, run a "sfc /scannow" to revert any incorrect permission changes.

Hi
Having previously formatted partitions, which did not work, I now deleted all partitions today, and reinstalled Windows 11 against 100% empty drive.
5 partitions have resulted on reinstall and NTLite "access denied" no longer shows and process completes correctly .
Weird but nothing more could have been resolved with previous Windows 11 installation .


Thank you and Nuhi for the effort. One thing was always certain , it was never going to be the product at fault.!