If I were a stick of rock and you’d cut me, many years ago, you’d have found the word Microsoft running through me to the core.
I game on XBOX, I develop software using Microsoft tools and I even used to (foolishly) adopt Microsoft products early.
The Armaitus of today is less of a Microsoft fan-boy or apologist and more of jaded ex-lover.
Whilst I upgraded to Windows 10 at home, for research purposes, I have resisted at work. Which is only a problem when you consider that I’m an IT Manager responsible for an estate of over 50 workstations.
Over the last day or so I have been trying to get a brand new Windows 10 laptop (Lenovo Thinkpad) onto our domain and working.
Thanks to to my decision to upgrade to Windows 10 at home, I was able to easily navigate through the various stages of adding the laptop to our domain. That side of the process was pretty much as you would expect and not really that much different as for Windows 8.
The problems started once I logged in as the domain user that would be accessing the laptop.
Neither the start menu, nor the Edge would start. Cortana remained silent.
A quick Google showed that I was not alone. From early this year to now, hundreds of Windows 10 users were suffering the same issue. Worse, there were a myriad of possible causes and solutions to the problem.
I’m writing this 24 hours later, solution in place and satisfied at a job well done. I’m also pretty annoyed that something so simple hasn’t been fixed by Microsoft yet.
My particular problems weren’t caused by a Group Policy we had in put in place – I’d list the cause as Microsoft not defaulting enough permissions throughout the system.
Microsoft would probably disagree and lay the blame at my not using a Group policy to manage my user’s system access to a granular level.
By ensuring that these permissions were granted on the laptop, the start menu became accessible once again.