In the new world of Modern apps, is there such a thing as a permanent path? I wondered this recently when assigning the new calc.exe to my keyboard hotbutton. The path is completely insane (and impermanent): C:\Windows\WinSxS\amd64_microsoft-windows-calc_31bf3856ad364e35_10.0.9926.0_none_849a092ad205aeb6 Calc.exe at the above path calls Calculator.Windows.exe here (also not a good path, and this can't be run directly from here anyway): C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_6.4.15.11_x64__8wekyb3d8bbwe
Thank god Classic Shell exists! Tisss Continuum terrible!! at least the old one has recent opened file list, and more, its basic and the best tbh.
That's because Server is not distributed in ESDs due to licensing. Each server is considered a major system. When you license e.g. Server 2012, you don't automatically get Server 2012 R2 (unless volume licensing with SA) vs. having Windows Client upgraded from 8 to 8.1 in retail channel. ESD is retail channel. MSDN/DS is another story. You need to assign Code: shell:appsfolder\Microsoft.WindowsCalculator_8wekyb3d8bbwe!App to your keyboard button as path to run. Do not link to exe's as Modern apps are run in appcontainer and are explicitly identified via their PackageFamilyName!AppUserModelID
Ah, that's good to know, and also uber-obscure. It works, but the MS Mouse and KB Center is going to need an update to support that new way, since it also displays an error (even though it actually runs it): "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
I have a good (educated) guess on this. FBL_Awesome was the January release and the reason they jumped to build 10,000 and released 9926 is because all builds after 9926 that had new features are 10,000 and above...they worked hard to stabilize 9926 for release but did not know the exact build number for releasing the Jan tech preview. So, what they did was jump to build 10,000 for features post Jan tech preview and kept 9920-9999 as options for the JTP and it happened that 9926 was stable enough for release but in this scenario, they could have compiled ~74 more builds to find a stable one for release. Now that this particular branch is done with, the next iteration needed a new name.
it would be extremely rash to release RTM in June, as xomniversex said, we should get a new build MUCH more often.. I'm waiting for Consumer preview instead of RTM
Patience everybody, a new build is coming this month for sure. hxxxs://twitter.com/joebelfiore/status/564537739849109504
I disagree. People and the media are judging the product on day 1 (remember the Xbox One launch!) Only 4 months and a lot of things are still completely missing. Nobody has ever tried the default browser, the XAML Start Menu misses the most basic features (drag&drop, JumpLists) the touch UI is extremely basic and there is so much old stuff still left behind (Media Player, personalization options, volume control and much more). Furthermore between BUILD and RTM are only 2 months time. That's not enough for developers to created new apps or update their existing apps. We don't need another Windows version without apps on day 1.