Windows 10: Microsoft extends Windows 10 version 1709 support because of Coronavirus

Microsoft announced yesterday that support for the company's Windows 10 version 1709 operating system has been extended by six months so that it is supported until October 13, 2020.

Enterprise, Education and iOT Enterprise editions of Windows 10 version 1709 are still supported while Home editions, Pro and Home for instance, are not. Microsoft ended support for these editions on April 19, 2019 already.

Support for Enterprise and Education versions of Windows 10 version 1709 was scheduled to run out on April 14, 2020 initially (after the Patch Tuesday of April 2020).



Microsoft explains that the current Coronavirus situation in the world is putting a toll on everyone. Many system administrators and IT workers work remotely and to reduce the workload that these IT workers have, Microsoft decided to postpone the end of support by six month.

We have been evaluating the public health situation, and we understand the impact this is having on you, our valued customers. To ease one of the many burdens you are currently facing, and based on customer feedback, we have decided to delay the scheduled end of service date for the Enterprise, Education, and IoT Enterprise editions of Windows 10, version 1709. This means devices will receive monthly security updates only from May to October. The final security update for these editions of Windows 10, version 1709 will be released on October 13, 2020 instead of April 14, 2020.
​

Microsoft will continue to produce security updates for versions of Windows 10 version 1709 until October 2020. These updates will be made available on the usual channels including Windows Update, WSUS and the Microsoft Update Catalog.

The end of support schedule for other versions of Windows 10 remains the same.Windows 10 version 1803 is set to run out of support on November 10, 2020, just a month after Windows 10 version 1709 support ends.

It is therefore recommended to upgrade to Windows 10 version 1809 or newer. Microsoft announced some time ago that support for the second feature update release of the year is extended to 30 months while support for the first feature update of the year is 18 month for Enterprise and Education customers.

Now You: Do you run Windows 10? Which version and why?

Thank you for being a Ghacks reader. The post Microsoft extends Windows 10 version 1709 support because of Coronavirus appeared first on gHacks Technology News.

read more...

 

Creative X-Fi Soundcards and Windows 10 Fall Creators Update 1709 = Complete Disaster / Not Working

Thank you for trying to help , i did tried your suggestion but it did not work :/ , nothing seems to make it work on Windows 10 Fall Creators Update 1709. In the meantime i have bought a new SoundBlasterX AE-5 and it did installed flawlessly , no problems whatsoever. it is up to Creative ( drivers ) and Microsoft ( bug fix ) to fix this huge bugs with Audio.

Kind Regards: Chispy

 

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

 

Unable to update Window 10 Pro version 1607 to version 1709

Have made several attempts to update Windows 10 version 1607 to the latest version 1709 and have not been successful.

I've done the following per some suggestions found online:

• Updated drivers
• Ran the Trouble Shooter for Windows 10 (Errors found were shown to be "Fixed" per the tool)
• Unplugged the printer
• Ran the DISM.exe

Although not at every attempt, I have received the following errors:

• 0xc1900101 - 0x30018
• 0x900704c7

Can someone please advise me as to what the errors are and provide me with the steps to update Windows.

Thank you