![]() ![]() And while some had workarounds, many did not. In just a day of testing-which involved installing the core apps I always use plus some purposefully challenging other applications for testing purposes-I ran into several problems. What’s not clear is whether the emulation solution software in Windows 10 on ARM will ever support 64-bit desktop applications or 圆4 Store apps. And support for 64-bit ARM Store apps is coming in a future update, possibly Redstone 5, which will arrive in September/October. (To be clear, Windows 10 on ARM is a 64-bit operating system. You cannot install 64-bit desktop (Win32) applications, or 64-bit (圆4 or ARM) Microsoft Store apps either. These include certain classes of apps (utilities that modify the Windows user interface, like shell extensions, input method editors (IMEs), assistive technologies, and cloud storage apps), x86/圆4 drivers, Hyper-V, and older games that rely on out-of-date versions of DirectX or hardware-accelerated OpenGL.īut the biggest limitation, and it’s a bad one, is that Windows 10 on ARM does not support 64-bit apps of any kind. ![]() The limitations imposed by ARM are a bit more complicated and are much less well-understood.Īs I reported back in February, Windows 10 on ARM drops several technologies and features that are available to those with x86/圆4 versions of the OS. This happens on the fly in just seconds, and it doesn’t even require a reboot. Escaping from this hell is straightforward and, best of all, free: You can switch to whatever full version of Windows 10 you’re using (today, Pro, but Home or Pro in the near future). You can only run the apps that come with Windows 10, plus those apps you acquire from the Microsoft Store. The S mode limitations are well-understood and easily bypassed. The issue here is multifaceted, and it involves two levels of limitations: Those imposed by Windows 10 S-soon to be S mode-and those imposed by ARM emulation. The types of users who would be drawn to this platform will be confused and frustrated by how often things don’t work. But Microsoft really needs to work on the user experience here. We’ve long understood that Windows 10 on ARM would present app compatibility compromises and challenges. Ultimately I could leave the user logged in all the time, and the computer unlocked, but obviously this isn't a desirable solution.Many of the apps I use everyday install and work with Windows 10 on ARM. The problem I'm running into is that when the user isn't fully logged in, or if the task starts when the user is logged in but the computer is locked, the app in question fails with a message that Direct3d failed to initialize.Ĭan anyone think of a way around this? Am I missing some configuration option (in Windows, the task scheduler, or DirectX)? Is there something I can do before launching this app that will force Direct3d to initialize? Is there a way to script a windows logon, so the user could be logged in (or the computer unlocked) before launching the app? I'm trying to automate this task using Windows Task Scheduler (on XP), and I've configured the task scheduler service to allow interaction with the desktop. I need to automate a build process that makes use of an app that initializes Direct3d as part of its initialization - even when it never needs to create a window. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |