Script runs but ends with errors and no .iso file is created when trying to create from Danish Win 11 ISO

[SteenSHansen]

I have just tried to create a tiny11 ISO-image from a Danish Windows 11-24H2 ISO-image downloaded in December 2024. I'm trying this on a virtual Windows 10 PC with all latest patches - before I go on to upgrade my real PC.
Various errors occur during the process and I have attached the tiny11.log from the process.
Do you have any idea about what is wrong? The Tiny11 script is downloaded today.

tiny11.log

[Miiraak]

It seem your machine can't reach https://msdl.microsoft.com/download/symbols/oscdimg.exe/3D44737265000/oscdimg.exe

PS>TerminatingError(Invoke-WebRequest): "Der kunne ikke oprettes forbindelse til fjernserveren"

Take a look at your internet connexion, firewall, proxy settings or retry it's maybe temporary. 🤔

[mondomata]

Error 3-4x ... What I need doing?

(my system is Windows X Lite Optimum 11) I want to write to tiny.iso the from Microsoft official Windows 11 Pro /hun iso media. But nov24 / ps1 script error is on the screenshot (THX!!)

[Miiraak]

@mondomata

Hi,
This error occure when you call your script without the right parameter or no param.

The $ScratchDisk is the working directory of tiny11.
You can set it, or let it empty and the script will use his root folder.

If you want to use your disk D:

.\tiny11maker.ps1 D

[mondomata]

Sorry, I tried, but error:

[Miiraak]

Re @mondomata !
If it's your only error, you should be able to create the iso.
As i said he take the script folder as scratch if an error occure so you will find the iso there.

Anyway, i've push a correctif a few days ago.
This will normally remove your error with scratch, take a look at #333.

[DataDry]

(Nearly) The same issue

I was usning 24h2 LTSC English (orig) and wasnt able to get the iso.

tiny11.log

Launched core version w/o any params and i can see the old iso only in the folder, as well as some new files (null, osc, log).

[Miiraak]

Hi @DataDry

That not really same. The coremake version use the $env: SystemDrive to set the output, which returns the drive that holds the Windows folder.
Take a look in your C: root

Note that coremaker is generally for tests, it's not suitable for uses, are you sure you need this one?

[DataDry]

@Miiraak

I checked the root of the C drive and found nothing related. I assume I should find something like a folder called tiny11 or an .iso file there, but I didn't see anything like that.

I was planning on using the resulting image for virtual machines and I don't think anything that is removed in the core version will be needed in my tasks, but thanks for your concern.

[Miiraak]

@DataDry
Okay, strange...
I'm not too familiar with the CoreMaker version. But in your logs all seems okay, however, I'll take a second look soon.
Yep, when it work, you will normally find a tiny11.iso in the folder.

GL with your tasks 😉
Yep, until you need an up-to-date windows, some security or a store/component acces the coremaker is fine.

[Miiraak]

Re @DataDry,
My bad, after look, the iso will normally be in the folder that hold the script.
Plus, there is effectly something wrong in your logs. I think i found why. 🤔

Can you retry but this time use the windows powershell as administrator not powershell 7 ?