Windows 10: Microsoft Edge gets WebP image support with Windows 10 Redstone 5 update

WebP is an image format developed by Google and works in web browsers like Chrome. Google’s WebP supports lossy and lossless compression and offers size reductions when compared to popular formats such as JPG and PNG.

The Chromium-based browsers like Chrome, Vivaldi and Opera have only supported the WebP format up until now. With the next big Windows 10 release codenamed Redstone 5, Microsoft is adding support for WebP image format to Edge browser. While that is certainly a good thing, support is limited to devices with Windows 10 Redstone 5.



Microsoft last also month published a new extension for Windows 10 that allows users to manually enable support for Google’s WebP media format in Edge browser. Not just Microsoft Edge, but other system applications will also support WebP image format.

Tip: WebP is supported in the latest builds of Microsoft Edge. https://t.co/VvyarwwBby

— Eric Lawrence (@ericlaw) July 24, 2018
​

Needless to say, Microsoft has put a lot of effort into making Edge the preferred choice for Windows 10 users worldwide, but Google Chrome is still the leading browser on the desktop with a share of more than 60 percent. Microsoft Edge is far behind Chrome and Firefox with a little over 4 percent market share.

The post Microsoft Edge gets WebP image support with Windows 10 Redstone 5 update appeared first on Windows Latest

Weiterlesen...

 

Two major Windows 10 updates scheduled for 2017




It may come as no surprise, but Microsoft won't release another major update for Windows 10 in 2016. The good news is you can expect two big updates to Microsoft’s latest operating system in 2017.

Microsoft let the information slip in a TechNet blog post published earlier in the week. “Windows 10, version 1607 is our third Windows 10 feature update released,” Microsoft said in the blog post. “Based on feedback from organizations moving to Windows 10, this will be our last feature update for 2016, with two additional feature updates expected in 2017.”

The blog post appears to confirm reports from the Windows rumor mill about the timing of the next two updates for Windows 10. The first update, dubbed Redstone 2, is expected to roll out in early 2017 with the second, Redstone 3, landing in the summer or early fall, similar to the timing of the recently released Anniversary Update (previously known as Redstone 1).

This schedule would put Microsoft back on a two updates per year schedule similar to the initial rollout of Windows 10, as Windows Central first pointed out. In 2015, Microsoft released Windows 10 (also known as Threshold) in July and then the November Update(dubbed Threshold 2) three months later.

This time around, Redstone 2 is expected to roll out in the spring and then Redstone 3 should hit about four to six months later.

The impact on you at home: Of the two updates, Redstone 2 looks to be the most interesting so far. Not necessarily because of the features, which are believed to be largely things that weren’t ready for the Anniversary Update. The big deal is that the early 2017 update is expected to roll out in concert with new hardware from Microsoft, asZDNet’s Mary Jo Foley first reported back in March.

Early builds of Redstone 2 are expected to roll out to Windows Insiders in the coming weeks.

Two major Windows 10 updates scheduled for 2017

 

Advice For People wishing to update to Windows 10 Redstone

There are Redstone images out there already.

 

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