error access files

[TOWUK]

i have full access / powershell 7 / admin privileges... original file from uupdump win 11 24h2 with updates:

tiny11.log

[ntdevlabs]

Have you tried using the standard Powershell included in Windows instead of Powershell 7?

[TOWUK]

Have you tried using the standard Powershell included in Windows instead of Powershell 7?

no...

[TOWUK]

i try standart powershell and dont have access sratchdir WTF?

[TOWUK]

[TOWUK]

[Elrondo46]

Same problems, lots of errors accessing. Error registry tweaks

Writing 946 files in 86 directories to E:\Users\ELYOAKE\Desktop\tiny11builder-main\tiny11.iso

100% complete

Storage optimization saved 3 files, 18432 bytes (0% of image)

After optimization, image file is 6095169536 bytes
Space saved because of embedding, sparseness or optimization = 18432

Done.
Creation completed! Press any key to exit the script...
Press Enter to continue:```

[ntdevlabs]

Apparently this issue was caused by icacls not taking finding the Administrators user group in languages where the word 'administrator' is spelled differently. An update was pushed that should fix this. let me know how it goes!

[Elrondo46]

Fixed changing all for: "Administrateurs" in french

[TOWUK]

win11 iso file (26100.268.240408-1720.GE_RELEASE_SVC_IM_CLIENTPRO_OEMRET_X64FRE_RU-RU) ‼️ okay, thx for some fix and regkey have errors! and other errors in next steps: tiny11.log

[juliendevops]

Hi, It may be possible to use the Admin group SID in the script, it should always be "S-1-5-32-544" as mentioned by MS itself (https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-identifiers).

It should be possible to use the actual name of the security group like this : $AdminGroupName = (Get-LocalGroup -SID S-1-5-32-544).name

It could be easier to use the SID for some commands and the name for others. I'm testing it but didn't have time to finish.

I'll try in the next couple of days.

[juliendevops]

Hi, It may be possible to use the Admin group SID in the script, it should always be "S-1-5-32-544" as mentioned by MS itself (https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-security-identifiers).

It should be possible to use the actual name of the security group like this : $AdminGroupName = (Get-LocalGroup -SID S-1-5-32-544).name

It could be easier to use the SID for some commands and the name for others. I'm testing it but didn't have time to finish.

I'll try in the next couple of days.

These changes have removed all errors related to accesses on my setup (french OS). Replace line 21 with these two lines if you want to test : $adminRoleSID = Get-LocalUser | Where-Object {$_.sid -like "S-1-5-21*-500"} $adminRole=[System.Security.Principal.WindowsBuiltInRole]::($adminRoleSID.name)