WaaS Assessment - Access is denied

AeonX

Well-Known Member
Messages
775
Reaction score
352
nuhi when removing WaaS this error message appears. Although if I load the image again in NTLite the component is no longer listed.

This only happens after sysprep and capturing the image to an install.wim

I am using NTLite 2.1.1.7917 but for a long time this has occurred even in older versions.

View attachment 4872

View attachment 4873
 
nuhi please don't forget about this as it is quite annoying.

I use sysprep as I integrate .net 3.5 and it leaves operations pending (pending.xml in WinSxS folder).
 
same problem here with WaaS
log says
03.09.2021 16:23:09 Removing: WaaS Assessment
03.09.2021 16:23:09 - SO: [5] Zugriff verweigert
03.09.2021 16:23:09 Error 5 at removing component registry entry: 3 | WaaS\UPFC | .
03.09.2021 16:23:09 Error 5 at processing registry
03.09.2021 16:23:09 WaaS Assessment - [5] Zugriff verweigert
 
Yes I didn't have the idea to look in the log. Looks like a problem with accessing some registry entry.

I use NTLite with NSudo so I don't have permission issues when adding .reg files (some entries it doesn't add) and still I get this error when removing WaaS.

EDIT:
My last log attached.
03/09/2021 22:10:26 Removing: WaaS Assessment
03/09/2021 22:10:26 - SO: [5] Access is denied.
03/09/2021 22:10:26 Error 5 at removing component registry entry: 3 | WaaS\UPFC | .
03/09/2021 22:10:26 Error 5 at processing registry
03/09/2021 22:10:26 WaaS Assessment - [5] Access is denied.
 
Last edited:
Hi,

I tested it a few times from another topic and could not replicate.

Do you have a preset for it? You can also DM me with it.
And do you enforce some extra security in the host OS, like Core Isolation and similar, if you have a list what to do in order to trigger this, let me know.

Thanks.
 
Hi,

I tested it a few times from another topic and could not replicate.

Do you have a preset for it? You can also DM me with it.
And do you enforce some extra security in the host OS, like Core Isolation and similar, if you have a list what to do in order to trigger this, let me know.

Thanks.
Made a bootable pendrive with Windows iso from Microsoft website. ctrl+shift+f3 at the oobe screen to enter audit mode and installed "startisback++". Then from the winpe environment of actual windows iso (which was downloaded from Microsoft) I open cmd and captured the modified windows iso(startisback++ installed) with dism to another drive. Then I applied Ntlite customisation on the "startisback++" installed iso.
 
Would be great to get that ISO in order to fix this.
I'll DM you.
Thanks.
 
The problem only occurs if you install Windows in audit mode, run sysprep, then capture the image to a new install.wim and then try to edit this image with NTLite. With an official ISO there are no problems.
 
Back
Top