I didn't watch the video but I think Its a pointless matter. What practically changes if the RTM (nowadays a pointless definition itself) will be 22000.768 or 22100.1? Just matter of "semantics", what's guaranteed is that today's version is not the "final" one, It will evolve until the official commercialization starts. Also IMO pretty sure that today's version is not time bombed anymore and will be updated by WU dozen of times until september/october
Not in my experience. The missing permission will be added to the foreign user profile, not replaced, just like a different user profile in single boot scenarios. In any case booting has little to do with a user profile, in the worst case a TEMP profile will be created That said there is a simple way to solve all the problem. Just create a domain (a virtualized server works just fine) and add all the multiboot users to it. Then each domain user will share the same SID and permissions across all multiboot installation.
I have noticed several things running DP on my Helios 300 laptop: 1- most of VPNs does not work properly, or does not work at all 2- Airpods pros connect fine but windows wont route sounds to it even though it saying it is using it as default device. 3- some animations kinda choppy 4- windows defender keeps turning off after each reboot. well i did not clean install, do you think these issues caused by upgrading from windows 10?
Was that what it was called? Thin PC? My bad. I never actually used it. I only ran into it after Win8 was around and I was still young and dumb and was super into tinkering with win8. Now I'm getting older and I just want the bloat to get off my lawn.
Thin PC was great once you pushed it to do more than it was meant to. Kept a netbook running nicely for a very long time - then 8.1/10 started overtaking it for how well they ran on the same hardware.
1 - Surfshark works for me no problem. 2 - JBL buds works as before (win 10) 3 - oh yeah 4 - same, feedback sent
Ok. I use it as one of my multiboot OSes, it's still great, light, still updated, thanks to PAEpatch3 it can see dozens of GB of RAM of modern machines,and last but not least it can run the official,unpatched, WMC package Hehe, I understand. There was a time I was young and dumb as well, I remember when I was excited by the release of Win95 OSR2 (and Fat32) I spent a couple of days (as inexperienced as I was) to understand how to force the upgrade, then to convert the old fat 16 to the new fat32, w/o losing my data. The result was that the space I got back, thanks to the smaller Fat32 clusters, was taken by the larger footprint of the new OS, in change everything was slower, because W95OSR2 was slower than Win95 RTM, and because Fat32 was way slower than Fat16. Fat32 was also way less resilient to unespected reboots (that at the time were normal) A loss-loss situation, but at the time I felt very proud of my efforts
Updated the tool to Win 11 Boot And Upgrade FiX KiT v1.8 https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v1-8.83724/ Changelog: Code: v1.8 Added the latest Diskpart & Apply Image v1.3.1 (@murphy78 removed the options for recovery, they are no longer supported by MSFT)
Updated the tool to Win 11 Boot And Upgrade FiX KiT v1.8 Does it work with windows in Spanish Language, or is it only for English Language?
Can someone make please the ISO from the UUP and upload on Google Drive? My CPU is not strong, it takes forever to create the ISO. Its the brazilian portuguese x64, the pro version.
Pl understand what he said . No any private build windows iso allowed on MDL. if found one shared by any user forums staff will take action asap.
perhaps if you make a single SKU version it not takes forever, if you try to build a whole business or client edition, which contain multiple images (like Pro/Enterprise/Education and so on, yes the process is repeated many times so it takes "forever"
Yea, neither do I unless it is a leak by WZor. I used to use those back in the day, but I make my own now. Hopefully my full explanation clears some things up for him.
A clean converted ISO should not need any explanation, only if you did anything else to it, and in that case, into the bin.