Do note that this system is liable to leave your computer vulnerable as it has no way to update itself from within the OS.
Yeah, as shsdowtofu points out below, you’re thinking of Tiny11 Core, which is the extra stripped down version that’s not recommended for most users.
Tiny11 can update just fine, it just won’t nag you to immediately update all the time like regular windows does.
I’ve been using Tiny11 as my secondary daily driver (my desktop main is stil running Windows 10) for a few months now, updating roughly once a month (with the option to do it more often if I want to) with absolutely no problems.
Are you sure that it cannot be updated? The GitHub readme sounds like updating Tiny11 Core is impossible (and it also lacks Windows Defender), implying that Tiny 11 can in fact be updated.
Also, for the very first time, introducing tiny11 core builder! A more powerful script, designed for a quick and dirty development testbed. Just the bare minimun, none of the fluff. This script generates a significantly reduced Windows 11 image. However, it’s not suitable for regular use due to its lack of serviceability - you can’t add languages, updates, or features post-creation. tiny11 Core is not a full Windows 11 substitute but a rapid testing or development tool, potentially useful for VM environments.
It literally says that it cannot be updated from a built OS install. You need to reinstall tiny11 by rebuilding the install image with a newer Windows 11 base image. Obviously it would be best to do this every time there is a security patch release for Windows 11.
EDIT: Rereading further, the bigger Tiny11 image might be able to be updated in-OS. I’m going to dig through the ps1 scripts to see if the README holds up to that un-noted capability.
EDIT2: I don’t see any registry edits that knock Windows Updater offline. I’ll test it in a VM to see if things work (from prebuilt when it eventually downloads). Though I am unsure at this moment if such an image’s changes will survive a Windows update at all.
EDIT3: VM not tested yet, but an issue on the GitHub seems to corroborate my initial assumption.
EDIT3: VM not tested yet, but an issue on the GitHub seems to corroborate my initial assumption.
Dude. That’s one user making an incorrect assumption. I’ve used it as my laptop daily driver for several months and updated a few times. It did NOT turn into Windows 11.
If that is the case, the developer should have likely noted otherwise before closing the issue as the final piece of discussion. That is good to know that your experience hasn’t dropped the OS into base Windows 11. If as you say is true, the developer should also really spend some time cleaning up the README and clarify that base Tiny11 can actually be updated in-OS. I will still test in a VM later today to confirm that Tiny11 doesn’t actually erode or degrade on update for myself.
It’s stated clearly in the documentation that CORE can’t be updated and is thus only recommended for testing and not as a daily driver, which is listed as one of the differences between base and core.
Do note that this system is liable to leave your computer vulnerable as it has no way to update itself from within the OS.
This image would be fine for booting short-term VMs as long as you periodically rebuild and reinstall it, but not ready for consumer use.
Yeah, as shsdowtofu points out below, you’re thinking of Tiny11 Core, which is the extra stripped down version that’s not recommended for most users.
Tiny11 can update just fine, it just won’t nag you to immediately update all the time like regular windows does.
I’ve been using Tiny11 as my secondary daily driver (my desktop main is stil running Windows 10) for a few months now, updating roughly once a month (with the option to do it more often if I want to) with absolutely no problems.
Are you sure that it cannot be updated? The GitHub readme sounds like updating Tiny11 Core is impossible (and it also lacks Windows Defender), implying that Tiny 11 can in fact be updated.
From the Github README:
It literally says that it cannot be updated from a built OS install. You need to reinstall tiny11 by rebuilding the install image with a newer Windows 11 base image. Obviously it would be best to do this every time there is a security patch release for Windows 11.
EDIT: Rereading further, the bigger Tiny11 image might be able to be updated in-OS. I’m going to dig through the ps1 scripts to see if the README holds up to that un-noted capability.
EDIT2: I don’t see any registry edits that knock Windows Updater offline. I’ll test it in a VM to see if things work (from prebuilt when it eventually downloads). Though I am unsure at this moment if such an image’s changes will survive a Windows update at all.
EDIT3: VM not tested yet, but an issue on the GitHub seems to corroborate my initial assumption.
Dude. That’s one user making an incorrect assumption. I’ve used it as my laptop daily driver for several months and updated a few times. It did NOT turn into Windows 11.
If that is the case, the developer should have likely noted otherwise before closing the issue as the final piece of discussion. That is good to know that your experience hasn’t dropped the OS into base Windows 11. If as you say is true, the developer should also really spend some time cleaning up the README and clarify that base Tiny11 can actually be updated in-OS. I will still test in a VM later today to confirm that Tiny11 doesn’t actually erode or degrade on update for myself.
It’s stated clearly in the documentation that CORE can’t be updated and is thus only recommended for testing and not as a daily driver, which is listed as one of the differences between base and core.
Happy testing, though 🤷