The work around didn't even last a session for me. after a restart i had it was back to the drawing board. I recalled that when installed the ProSet it had asked me if i wanted it to be the primary manager for networks and i said yes. after which point i was not longer able to use (or regain use) of Windows Connection Manager. Well, since the ProSet wasn't able to manage the wireless connections and now that windows was no longer allowing me access to manage my wireless connections i had to do a soft reset on my entire system (after i had to painstakingly back up my entire system). so far the issue seems to no longer persist but i will try to do a few shutdowns and restarts to verify that the issue is no longer continuing. will update my results through out the day.
↧