ntdevlabs
Erros (maybe not yet 25H2 Compatible?)
Seems like its hopeless to use this for me. It keeps making insane amount of errors. End result is a big nothing. I don't understand why you try to make scratchdisk and tiny11 folder on the system drive's root in the first place. You will need extra permissions that you clearly don't have access denied. You have this even if you start Power Shell as admin, the script need additional privileges I'm pretty sure, what I cannot grant. Why don't you just use the same folder where the tiny11 builder resides? Really I don't undestand. Anyways, last time I had similar errors, you closed the case, others tried to push me to another different "updated" installer that was like 500% bigger than yours so I'm sorry I won't trust those huge crazy powershells not sure what they do and I won't start it with admin permission on my PC.
Your builder looks fine, but it seems you keep trying to push processes that are out of bounds and system won't give you permission simple as that. AND the other issue that maybe I shouldn't try with the latest windows installer? :D
UPDATE: Trying again, this time with Windows11_InsiderPreview_Client_x64_en-us_27924.iso, so far I saw only a few errors, and look behold! The scratch disk and the installer folders are within the d:\Tiny11Builder folders, so this is more promising! Yes both time I've used your standard command line method written on the main page, so no difference there. Updating once it finished this compilation with log file.
So there is really no error this time, using the above mentioned iso. And my path interestingly were the same as before Isopath E, Installpath D, but now nicely everything done within the D:\Tiny11\D folder inside the script's folder.
So I assume the new updated windows isn't supported yet. :D Still, what caused the issue of permission errors and that tiny11 tried to create scratch on C: and install also on C: root folders I got no clue, used the same parameters every time.
I'm going to try this iso now on my small surface book 2 👯
I second this, the output should just accept a path so you can put it wherever you like, not just a root drive letter
I've managed to create a tiny11 iso from windows 11 24h2, but its like 600MB bigger than the insider version I wonder why. I don't see any error messages.
However I don't think the path command line is actually working both times when the process was successful and working I had to type the windows install path the second time, even though it was set with -ISO D -SCRATCH D parameters.
Seems like its hopeless to use this for me. It keeps making insane amount of errors. End result is a big nothing. I don't understand why you try to make scratchdisk and tiny11 folder on the system drive's root in the first place. You will need extra permissions that you clearly don't have access denied. You have this even if you start Power Shell as admin, the script need additional privileges I'm pretty sure, what I cannot grant. Why don't you just use the same folder where the tiny11 builder resides? Really I don't undestand. Anyways, last time I had similar errors, you closed the case, others tried to push me to another different "updated" installer that was like 500% bigger than yours so I'm sorry I won't trust those huge crazy powershells not sure what they do and I won't start it with admin permission on my PC.
Your builder looks fine, but it seems you keep trying to push processes that are out of bounds and system won't give you permission simple as that. AND the other issue that maybe I shouldn't try with the latest windows installer? :D
i think found a fix by just creating a shortcut for the ps1 file and running it with ( C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe ) let me know if you have questions. it also seems to be working with 25H2.
Hi ! Did you try with the script on the main page ? Not the one in release. He's out-to-date.
I had the same problem as 40P3 and i used the script file from the main page as you mentioned. However, i did find a fix by just creating a shortcut for the ps1 file and running it with ( C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe )
That's stange, it's maybe a workaround for something I'm not aware of. But, we are missing some information; perhaps you're right, but as it is, nothing proves that you and 40P3 had the same error. I would like to know if your solution works for 40P3, it could be interesting.
For me, if you need to create a shortcut to the script with "Start in" set to PowerShell, it is that the terminal you use is not the right one.
Do you mean I shouldn't use the terminal app, or that I should use it? -------- Original message --------From: Old Character @.> Date: 11/5/25 1:05 PM (GMT-06:00) To: ntdevlabs/tiny11builder @.> Cc: the fitnessgram pacer test is a multistage aerobic capacity test @.>, Comment @.> Subject: Re: [ntdevlabs/tiny11builder] Erros (maybe not yet 25H2 Compatible?) (Issue #484) Miiraak left a comment (ntdevlabs/tiny11builder#484) That's stange, it's maybe a workaround for something I'm not aware of. But, we are missing some information; perhaps you're right, but as it is, nothing proves that you and 40P3 had the same error. I would like to know if your solution works for 40P3, it could be interesting. For me, if you need to create a shortcut to the script with "Start in" set to PowerShell, it is that the terminal you use is not the right one.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
And for the record, when I use the command in powershell from the readme.md page, I get countless access denied messages even though I ran it as an administrator. -------- Original message --------From: Old Character @.> Date: 11/5/25 1:05 PM (GMT-06:00) To: ntdevlabs/tiny11builder @.> Cc: the fitnessgram pacer test is a multistage aerobic capacity test @.>, Comment @.> Subject: Re: [ntdevlabs/tiny11builder] Erros (maybe not yet 25H2 Compatible?) (Issue #484) Miiraak left a comment (ntdevlabs/tiny11builder#484) That's stange, it's maybe a workaround for something I'm not aware of. But, we are missing some information; perhaps you're right, but as it is, nothing proves that you and 40P3 had the same error. I would like to know if your solution works for 40P3, it could be interesting. For me, if you need to create a shortcut to the script with "Start in" set to PowerShell, it is that the terminal you use is not the right one.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
You can send us your full command and the log file that can help.
yeah the command i used that ended in a bunch of error messages was this: .\tiny11maker.ps1 -ISO D -SCRATCH D here's the log file:
Okay, I see.
ISO and SCRATCH cannot be the same value.
The ISO parameter is the image you mount and SCRATCH is the working folder for the script. It needs to be a partition on a storage disk.
Assuming your iso was mounted on D. You have only one partition to use C or you can use a USB key but I do not recommend it (unless you have a good one)
Okay, I see.
ISOandSCRATCHcannot be the same value. TheISOparameter is the image you mount andSCRATCHis the working folder for the script. It needs to be a partition on a storage disk. Assuming your iso was mounted on D. You have only one partition to useCor you can use a USB key but I do not recommend it (unless you have a good one)
i couldn't figure out what i should write for the working folder for 'SCRATCH', there were some errors that kept popping up ; edit: turns out i just needed to type in 'c'