Project: Tiny Windows Ultimate

[Karl-WE]

@Belim and community have you ever considered teaming up with Tiny11 project? I have actively contributed there. I could imagine there are some shared ilar targets or routines.

Project idea:

• Creating a project that is
• forking tiny11, optional support of Microsoft account login for security, Windows Backup / Restore and licensing transfer reasons.
• Adding flyoobe
• Adding winslop routines (if not duplicated like app removal), to the native oobe screens
• using winget import / export for faster redeployment
• Eventually adding Uniget UI, changed responsibility of ownership but still free and open-sourced.
• implementation of Secure Boot CA2023 certificate renewal status and remediations
• adding my configuration best practices.
• adding winslop into the oobe process after tiny 11 deployment

Expectations:

• targeting lowest footprint on valuable SSD and NVMe, RAM considering today's prices.
• Super fast image deployment / re-deployment / assisted with winget capabilities.
• maintaining highest security standards with Defender and Core isolating features
• targeting both tiny11 and winslop userbase
• integrating Security Baselines based on Microsoft OSconfig for client OS profile.

Sidenote:

• considering removal (or switch to private) of older repos of earlier projects that do similar things as winslop today. I think there are some historical and duplicate products.

My suggestions for participation:

• providing ready to use PS code for the secure boot part
• testing
• find more things to debloat
• observe (folder and number of files). In this regard I have noticed a huge drop from 26100 "25H2" build to the Canary 29000 "possible 27H2". Microsoft does actively debloat files and folders in c:\windows and program files.
• promoting releases
  -- LinkedIn
  -- techcommunity.microsoft.com blogpost
  -- askwoody.com (huge potential for new users).

expanding the current channels like deskmodder (Jürgen), computerbase.de, Golem.de