As I tested out the Windows 10 Technical Preview build 10061 for the first time, I noticed a slight problem. When I tried to open Windows applications (Win32) like Microsoft Office, which I use a lot, it simply would not open. The first couple times I thought it was something wrong with my PC or I was missing something, so I tried to open other Win32 desktop apps, to no avail.
So I tried the newer apps that came out with Windows 10, like Mail and Calendar and they opened up just fine. So I started to wonder what was going on until I read up on the write-up by Gabe Aul on Windows 10 build 10061. Aul details new improvements and features, and finally I get to the part where there are know issues and bugs. I stopped dead in my tracks. Aul states:
“We know this one will be a bit painful but there is a bug with this build in which Win32 (desktop) apps won’t launch from the Start menu. The workaround is to use search to find and launch these apps and pin them to your taskbar for quick access.”
Saying that the inability to launch Win32 applications from the Start menu “is a bit painful” is an understatement. I use many Win32 applications (not all of them daily), so I can’t imagine pinning every one I use to the Taskbar. I don’t think I have enough room and I have an enough of a hard time trying to find Win32 applications by icons alone. It would be nice to just open the Start menu and open the application I want to use with no problems.
So, it looks like for now, I will have to wait until the next build or until an update releases to fit the issue. It’s not “painful,” it’s a very annoying pain in the ass. For now, I will just have to deal with it like everyone else, and I have to keep in mind that I am just using a preview build. So for now, at least, I will have to allow this known bug to drive me insane.Further reading: Gabe Aul, Microsoft, Office 2010, Windows 10