I'm running Open-Shell-Menu, Stardock Windowblinds, 8Gadgetpack, and Explorer Patcher all at the same time. Except for the desktop icons, it looks just like Windows 10. Of course, I'm walking on thin ice all the time and at risk for Windows 11 getting wonky. I guess I don't mind living dangerously.
UUP conversion isn't that troublesome, it's basic wim conversion / updating could be UEFI and/or secure boot related
Do you mean this? Turning on or off any feature from here? Then yes. I was not aware of this behaviour.
Ive not observed it with a CU update though , only a full installation but i guess it can apply to CU's if theres updated packages (in cu) that got missed or just needed upgrading
The more I look in to it the more the matter becomes darker. I built another 22621 ISO, deployed it and it doesn't work as well. I have literally dozens of installations all with the same driver loaded w/o any problem (it's rtcore64.sys from rmclock) including Win11/Server11, they are all working except all 22631 I tested and now also a 22621, the driver won't load even using F8 from the boot menu. Frankly I couldnt care less if a specific build is unsable for me, but having no idea about what's different on those builds drives me crazy. P.S. It's all MBR so no secure boot is involved (at least that's the theory )
That's the win11 problem. To have usable you need to make it identical to win10, with the start menu from win7 and the gadgets from vista (and some go further using the classic theme from win 2000). P.S. perhaps StartAllBack (with or w/o classic shell), is enough to get back most of the usability in one shot
Open-Shell brings back the Windows XP, 7, or 10 start menu on Windows 11, but you won't see the menu unless you assign a graphic for the start menu button. Explorer Patcher brings back the Windows 10 task bar. So if you're running Open-Shell and Explorer Patcher together, you don't have to assign a start menu graphic in Open-Shell for the start button. Windows 11 looks and runs like Windows 10. Those two programs are free and don't fight with one another. Stardock Windowblinds and 8Gadget pack are optional.
Damn ...guys dont enable hpet in bcdedit(useplatformclock) jeez, 100% cpu usage and i couldn't do anything lol I do dumb things when im bored, maybe its related to memory integrity? who knows ..it certainly doesn't work with beta Its not supposed to affect the system that way i just wanted to test games with and without it i remember doing benching in win10 and it worked just fine ...not much between enabled and disabled
I know what explorer patcher does, but StartAllBacks does practically what explorer patcher + classic shell do. But you can turn off its own start menu. In that case Classic Shell will start normally. just like it does from Vista to Win 10. Explorer patcher is free and nice (I use it on win 10), but the author don't care much about Server 11 and most advanced builds. StartAllback is usually more compatible. Whatever MS managed to broke both of them in builds 259xx (no systray)
New! This update adds a new hover behavior to the search box gleam. When you hover over it, the search flyout box might appear. You can adjust this behavior by right-clicking the taskbar. Then choose Taskbar settings to change your search box experience. /// how work this ?i dont see in settings !
Calm down child no1 called names just because all your doing is crying every day or second day over an OS like uve no actual other life outside the internet ya asked a question ya got an answer dunno why me original comment got deleted for unless ya went crying about that as well
Imagine posting like this twice. Kind of ironic saying someone has no life when you took the time out of your day to troll, then notice your troll post was deleted, comment about that, then troll again. Seems like you need to look in the mirror and stop calling the kettle black.
This seems like a rather clueless comment to make when you know what he is talking about don't you think?