I do however run it on my Surface 2 still and it's quite reasonable all things considered. ![]() I never got the chance to run it on my Surface RT, sadly it had an unfortunate encounter with a concrete floor. Johndoe123 wrote:On a side note, has anyone tried installing 15035 on a Surface RT yet? If you have any comments on this idea or think of a way it could be done, I would love to hear about it, so be sure to reply to this thread in that case. Basically, it would take a Surface Pro X version of Windows 10 (from recovery media created for one, unless you’re a pirate), and replace the Surface Pro X drivers with those of a Windows RT tablet of your choosing. This would be even cooler if you could upgrade from Windows RT to Windows 10 without doing a clean install, as if you were installing a Windows 10 feature update.Īnyway, I have an idea for a utility that has this purpose and how it would work. The same could go for other tablets that run Windows RT. All it would probably require is the correct driver support, which should be able to be ported over from Windows RT 8.1, considering that Windows 10 is based on Windows 8.1, and Windows 8.1 and its RT counterpart share the same code base. I’d like it if the version of Windows 10 that runs on the Surface Pro X could be modified to run on the Surface RT, Surface 2, and other Windows RT tablets. The Surface Pro X runs Windows 10, so I think that the basis for running it on Surface RTs and Surface 2s is there. It has a Microsoft-designed ARM CPU, yet it can still run 32-bit Win32 apps via emulation. One of Microsoft’s current Surface tablet models is the Surface Pro X. The tablet has an ARM-based CPU, and therefore runs Windows RT, the sibling of Windows 8 that prevents Win32 applications from being executed. "If there's no other option, then security vendors need to understand whether an attacker could gain control over processes, how to detect it and stop it before it happens.I have an old Microsoft Surface 2 tablet from around 2014. Otherwise, it's up to applications to stop trusting other processes by default – even if they are created by Microsoft, Yair told us. Microsoft, at least, has released a fix to address the problem Yair found, we're told, while Crowdstrike, CyberReason and Palo Alto all patched their EDRs. Is there any way to defend against such attacks? So, if an attacker can manage to hijack a Windows workstation, they could feasibly encrypt a good portion of the machine using a legitimate piece of software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |