-
-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lastest iso (24H2) unsupported? #263
Comments
The script is trying to directly access the mounted registry hives through the |
adding to @doums |
|
Same for me it keeps building and completing and tons of errors and when i use it to install. Nothing is removed everything still gets installed. |
Well I tried again and I’m getting same errors
…On Wed, Nov 6, 2024 at 10:23 PM Karl Wester-Ebbinghaus < ***@***.***> wrote:
Have a look at the revised Code in #268
<#268>
You have to start it
Windows + X
Terminal (Admin) console, PowerShell
.\tinymaker11.ps1 -scratchdirectory yourdriveletter
Tested it with 24H2 and works fine.
The issues were more code related than specific to a release.
@Xenshen <https://github.com/Xenshen>
—
Reply to this email directly, view it on GitHub
<#263 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BMGX5S5B2FVQPAKKPV73JNTZ7LMMNAVCNFSM6AAAAABQ7KP5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRRGIZTMMBQGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Included the log |
I've got problems with 24H2. While installing it will crash at 10%. |
Just got to windows website and download the iso it's the latest release.
Good question where you can get one older from a trusted source
…On Sun, Nov 10, 2024, 10:43 AM Ismael Núñez Carrión < ***@***.***> wrote:
I've got problems with 24H2. While installing it will crash at 10%.
How can we get a previous stable windows release from safe source?
—
Reply to this email directly, view it on GitHub
<#263 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BMGX5S3JF3UR6RHGDRBE7STZ755IZAVCNFSM6AAAAABQ7KP5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWG44DEOBQGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This is the only official source from Microsoft for home users |
#268 has been merged into Main Branch. With this, the errors mentioned should be resolved. Please Download the latest file. Please do not use context menu but execute the script from Microsoft Terminal PowerShell 5.1 / 7.x. Hope that the issues are resolved. Please close if it's working or comment. |
Thank you so much for your help. I am getting the same errors - "Requested registry access is not allowed" and similar "null value expression" errors despite following these instructions. Potentially the problem is with the Scratchdisk parameter. You suggested: .\tinymaker11.ps1 -scratchdirectory yourdriveletter I tried several variations of: .\tiny11maker.ps1 -C:\Users\tiny\ C: and it flashes up a momentary error about the scratchdisk parameter being wrong, before continuing anyway and giving those errors. If my parameters are the issue, can you please give me the exact syntax? I am using the latest 24H2 iso from Microsoft. I have attached the log file below: `********************** Transcript started, output file is \tiny11.log ImageIndex : 1 ImageIndex : 2 ImageIndex : 3 ImageIndex : 4 ImageIndex : 5 ImageIndex : 6 ImageIndex : 7 ImageIndex : 8 ImageIndex : 9 ImageIndex : 10 ImageIndex : 11 Mounting Windows image. This may take a while. Path : \scratchdir Default system UI language code: en-GB Removing Edge: InvalidOperation: C:\Users\tiny\tiny11maker.ps1:347 InvalidOperation: C:\Users\tiny\tiny11maker.ps1:348 InvalidOperation: C:\Users\tiny\tiny11maker.ps1:349 InvalidOperation: C:\Users\tiny\tiny11maker.ps1:350 Owner changed to Administrators. InvalidOperation: C:\Users\tiny\tiny11maker.ps1:353 InvalidOperation: C:\Users\tiny\tiny11maker.ps1:355 InvalidOperation: C:\Users\tiny\tiny11maker.ps1:356 Permissions modified for Administrators group. Deleting Application Compatibility Appraiser Cleaning up image... ImageHealthState : Healthy Cleanup complete. Unmounting image... LogPath : C:\Windows\Logs\DISM\dism.log Exporting image... ImagePath : \tiny11\sources\install2.wim Windows image completed. Continuing with boot.wim. Path : \scratchdir Loading registry... InvalidOperation: C:\Users\tiny\tiny11maker.ps1:429 The operation completed successfully. LogPath : C:\Windows\Logs\DISM\dism.log The tiny11 image is now completed. Proceeding with the making of the ISO... OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Scanning source tree (1000 files in 97 directories) Computing directory information complete Image file is 5644025856 bytes (before optimization) Writing 1057 files in 103 directories to C:\Users\tiny\tiny11.iso 100% complete Storage optimization saved 66 files, 15710208 bytes (1% of image) After optimization, image file is 5630803968 bytes Done. Performing Cleanup... PowerShell transcript end ` |
Alright, I figured out what you meant with the syntax - I believe you meant .\tinymaker11.ps1 -ScratchDisk yourdriveletter Anyway, I tried this - but still get those numerous registry errors. To confirm, this should still be working with 24H2 Pro, right? Which is what I'm using. |
I will try to invest more time on helping with this issue. However I really would focus on the feature PRs before fiddling on testing scratchdirectory to other location. I needs complete different logic. I am not speaking for the maintainer. Please free up space on C if you need it. If there's space on C do not pass any parameter. Otherwise could provide an Image to share on OneDrive. |
Hi, I successfully built the image via
tiny11Coremaker.ps1
script fromWin11_24H2_French_x64.iso
.But when trying to install it on a vm (qemu/kvm), after disk partitioning, the installation process fails at 10% "Windows installation has failed".
EDIT: image built from
tiny11maker.ps1
installs with no issueAlso, there are a bunch of registry errors emitted while running the script
The text was updated successfully, but these errors were encountered: