cj_arizona

Hello all! Now that the new release is out (Start 11), how do you sign up to beta the next version and the beta program in general? Thanks!

Hey Paul! Thanks for looking into this. I did have Window Blinds installed as well as Adobe Premiere Pro (video editing) and Photoshop (my photography) both video-taxing apps. I uninstalled WB, but still had no success. I messaged a contact at MS about another issue and through a lot of troubleshooting and investigating--despite the fact I was not on an Insider Build (not for a long while), the "control-scroll-lock" trick gave me the GSOD and said "Your Insider preview has run i

Yes. All of the above work was done in the sandbox. Most of it was done on an actual PC as well. There is some common hardware component or card in a Dell , as the chance of this occurring across three different PCs, different 'realities' (ie sandboxes). I just don't know what it is. Unfortunately I don't have a PC with an AMD chipset to see if that makes any difference. Since your NVIDA card works fine, that takes the NVIDA or graphics card card off the table as a possibility.

I tried the following in that environment 1) Installed Windows and updated with these scenarios, and a fresh install each scenario -Current Version: No Transparency -Original Install: v 1.2.x; Result: No transparency reads as "Preview Version of Windows 11"; Beta Install: Result: No transparency. 2) Downloaded and executed the purge program each time, then not each time: Result: No transparency, Did not run purge on above scenarios: Result: No

There you go!

Thanks for the help! I did exactly as you said and it is still a no-go, If there was a way to post a screengrab I would.

Hello all! I am having an odd issue across multiple machines. Any public build after 22H2 22621.819, and the taskbar loses transparency. It is still controllable by the slider, but the slider does nothing. The start MENU does work. I have tried: rolling back to this build after Nov patch, Dec patch and Jan patch. In short I have "waited" for MS to resolve the bug. I have tried to uninstall and reinstall start 11 (ironically the version current last April works--update to