A lot of errors, latest Windows 11 24H2

[capsload2]

Im getting a lot of errors, trying to build a Tiny11 with the latest Windows 11 Pro.

[Vanqy9316]

thanks for submitting this issue. can you please verify that you have started the script as an administrator? Even if you end up getting a .iso file at the end of the script, it will not work unless its on full privileges.

Please try again with the following steps:

• copy the script file, e.g. C:\Users\Vanqy\Desktop\Tools\tiny11builder-main\tiny11maker.ps1 to clipboard
• Start PowerShell/Terminal as admin via the start menu or powertoys run.
• type powershell -f ,paste from clipboard and hit enter. the full command should look like this powershell -f C:\Users\Vanqy\Desktop\Tools\tiny11builder-main\tiny11maker.ps1

when the script is done, notice the size difference of the resulting .iso

the last two days, ive tested multiple times of not using and using powershell -f to run the script. without the command, even in a admin privileged powershell, the resulting .iso was not working and failed in midst of setup: "cannot validate product key". upon search on the internet, i stumbled upon this: system can't access the file on the usb flash drive to validate the key

cheers

[robinhood2014]

Please try again with the following steps:

• copy the script file, e.g. C:\Users\Vanqy\Desktop\Tools\tiny11builder-main to clipboard
• Start PowerShell/Terminal as admin via the start menu or powertoys run.
• type powershell -f ,paste from clipboard and hit enter. the full command should look like this powershell -f C:\Users\Vanqy\Desktop\Tools\tiny11builder-main

That got it working. It would help the user greatly if we were to explicitly specify that this tool requires the built-in Windows PowerShell, not the new cross-platform PowerShell Core. Also, we don't want to forget the name of the actual .ps1 file in the path, thus: powershell -f C:\path\to\tiny11builder-main\tiny11maker.ps1 or powershell -f C:\path\to\tiny11builder-main\tiny11Coremaker.ps1.

[Karl-WE]

@robinhood2014 @Vanqy9316 the tiny11maker (PowerShell) the script works with PS 5.1 and PS 7.x in PowerShell. Last check PS 7.4. Please elaborate.

[Vanqy9316]

@Karl-WE i do not know if i speak for OP or anyone else, but i elaborated the issue and my solution as good as i could. If you require more specific information which i am unaware of, please disclose, so further steps can be taken to solve this issue fully.

[Karl-WE]

@Vanqy9316 please repro:

download the latest tiny11maker (not core) download latest W11 24H2

put that in DL folder on C: drive
Windows + X > Terminal (Admin)
nav to DL folder
gci tiny*.ps1 | unblock-file

execute the script upload the log please.

[Vanqy9316]

@Karl-WE

unknown command: "gci"

[Karl-WE]

Are you sure you are executing the script in Windows 10/11 Microsoft Terminal? Error indicates you are in a legacy command line (cmd). The script requires PowerShell 5.1 or 7.x.

Thanks.

[Vanqy9316]

@Karl-WE yes, i am using the new Microsoft Terminal. The error is not related to PowerShell afaik. See attached picture:

[Karl-WE]

OK I see the point. Please go to Microsoft Terminal Settings and change default to PowerShell. Also choose from default console host to Microsoft Terminal. This will do it.

[Vanqy9316]

@Karl-WE thanks for your reply. however the changes you suggested are slightly misleading: opening the terminal should by default open the new command line and not powershell (user preference) and by opening the terminal there was, unfortunately, the ambiguity of opening new command line or PS/pwsh.

i went ahead and ran gci tiny*.ps1 | unblock-file with pwsh as administrator and immediately ran tiny11maker.ps1 the created tiny11.iso then was tested in Oracle VirtualBox to verify if the script worked. unfortunately, the .iso is faulty, see screenshot (same issue as #309 ):

the log:

tiny11.log

the log however contains zero useful information (my guess). the highly scuffed scratchdisk logic from the script defaulted back to root of drive C (where the log was found). i never got asked to define the scratchdir. What about of just using the %TEMP% folder of the currenUser? seems too simple? however i only have assumptions of what scratchdisk or scratchdir is, i might be mislead at this point.

neither contains the log any of the error hell i got during running the script, which seems weird. is there any verbose or debug arg i can use to run the script? my last attempt to read trough the script got me quite overwhelmed .

[Karl-WE]

Oh dear. I think this is out of my hands. We need help and some PRs from @ntdevlabs

[Vanqy9316]

@Karl-WE thank you for your help though. my solution however is still valid and works. dont ask me why it works, but it does.

[ItzELECTR0]

* type `powershell -f` ,paste from clipboard and hit enter. the full command should look like this `powershell -f C:\Users\Vanqy\Desktop\Tools\tiny11builder-main\tiny11maker.ps1`

This should be mentioned in the README. While following the current README instructions you will get the Product Key issue and bash your head against the wall trying to find out why. (Took me a good while to find this solution)