Greg, in a situation like this the only thing that comes to mind (after all the usual searching and reinstalls you've already tried) is to search the windows logs for any clues. Also perhaps work machines are some obscure hardening/firewall/similar type settings that are blocking call out/in and the software behaving stupidly based on that.
<vent> As the decades go on, the obscurity of trying to find things going wrong in windows is pushing me farther and farther away from recommending/wanting to build software on it. Perhaps I'm just getting old and tired ;-) </vent> Sorry, I can't offer anything else and I hope you get a resolution. regards, Preet, in Auckland NZ On Sun, 11 Sept 2022 at 11:10, Greg Keogh via ozdotnet < ozdotnet@ozdotnet.com> wrote: > Folks, my Windows Forms toolbox is empty for .NET 6 projects. I've > expended hours on web searches and "Resets" and experiments but it's > utterly hopeless. I've run out of ideas. > > The problem is only on my work PC, not my idental laptop or in a VM. Has > anyone experienced this and fixed it? There must be something peculiar > about my work PC, but what?!? > > I could start randomly uninstalling and installing stuff again, but that > could go on for days with no promise of a fix. Why does crap like this > happen so often? Sometimes I spend more time keeping my PC and development > environment working than I do actually writing software. > > *Greg K* > -- > ozdotnet mailing list > To manage your subscription, access archives: https://codify.mailman3.com/
