Windows 10: Microsoft is bringing graphics processor support to Linux on Windows 10 through its Windows...

Microsoft just gave Linux on Windows 10 a major upgrade By Anthony Spadafora

GPU support is coming to Microsoft's Windows Subsystem for Linux.

Microsoft is bringing graphics processor support to Linux on Windows 10 through its Windows Subsystem for Linux (WSL) and now Nvidia, Intel and AMD have announced their support for the effort as well.

Back at Build 2020, the software giant revealed its plans to add a full Linux kernel to Windows 10 with the release of version 2 of WSL and the company also now plans to support Linux GUI apps that can run alongside regular Windows apps. By adding GPU support to WSL, Microsoft aims to bring the performance of applications running in WSL 2 closer to those running on Windows.

Program manager for the Windows API Platform Team, Clarke Rahrig explained in a blog post that GPU compute support is the most requested feature among WSL users, saying:

“Adding GPU compute support to WSL has been our #1 most requested feature since the first release. Over the last few years, the WSL, Virtualization, DirectX, Windows Driver, Windows AI teams, and our silicon partners have been working hard to deliver this capability.”

.“Adding GPU compute support to WSL has been our #1 most requested feature since the first release. Over the last few years, the WSL, Virtualization, DirectX, Windows Driver, Windows AI teams, and our silicon partners have been working hard to deliver this capability.”

GPU support for WSL is now available in the Dev Channel preview of Windows 10 build 20150. The 20150 update adds support for GPUs from Nvidia, AMD and Intel as well as Nvidia's CUDA parallel computing platform and Microsoft's Direct ML (Direct Machine Learning) API.

submitted by /u/reddit007user
[link] [comments]

:)

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer

 

Windows 10 Creators Update ends support for Intel’s Clover Trail processors.

BAM and there it is.

http://www.pcworld.com/article/3208...orted-on-this-pc-error-clover-trail-atom.html


Devices with these Intel “Clover Trail” processors are impacted:

• Atom Z2760

• Atom Z2520

• Atom Z2560

• Atom Z2580

 

Intel HD 630 (Kaby Lake) graphics drivers for Windows 8.1 64

Neither Intel nor Microsoft support Kabylake under Windows 7 or 8.1

Check out Microsoft's statement:
The processor is not supported together with the Windows version that you are currently using" error when you scan or download Windows updates

Then check the release notes from the driver linked above:
OS support
On 7th Generation Intel® Core™ Processors, Intel® Xeon® Mobile Processors and related Intel® Pentium® Processors/Intel® Celeron® Processors:

• Microsoft Windows® 10* 64-bit only

Regarding the versions: last four digits indicate the actual driver number as described at Understanding the Intel® Graphics Driver Version Number