Windows 10 News and Announcements...

add this one too, Papusan:
from Askwoody - Are Win10 version 1909 users bing pushed onto version 2004?
https://www.askwoody.com/2020/are-win10-version-1909-users-being-pushed-onto-version-2004/

 

Microsoft begins pushing the 'new' Microsoft Edge browser to all Windows 10 PCs pcworld.com | June 05, 2020

Microsoft has begun replacing what it calls the "legacy" Microsoft Edge browser with its Chromium-based "new" Edge browser, via a Windows Update.

Microsoft began updating PCs to the new Edge in January. It began with PCs still running the April 2018 Update, also known as version 1803. Now, the new Microsoft Edge is being made available to the Windows 10 versions after 1803, up through the Windows 10 May 2020 Update, aka version 2004.

 

Good to have a choice of privacy tools available, a new one, something to test & support?

https://www.mirinsoft.com/blog/19-apps/33-check-your-privacy-state-with-spydish

 

More beautyful from Redmond.

Windows 10 May 2020 Update is causing issues with Intel Optane Windowslatest. com | June 4, 2020

First unveiled in 2017, Intel's Optane is a memory module designed to improve desktop and laptop performance for less money. It appears that Windows 10 May 2020 Update, which was released to mainstream users in May, is not compatible with some Intel Optane memory modules....

If you force the update via Media Creation Tool, your PC is likely to run into compatibility issues. During the update process, Windows 10 removes one Optane Memory Pinning file from the device, but it would still try to run it and this leads to multiple errors and even performance issues.

 

F00king amateurs at Redmond

 

Nothing surprises me from a company that can't make a proper Start Menu!

There is also a Disk Optimize and Defrag bug, you optimize/defrag a disk, then it says last Optimized (0 Days ago). Exit the tool and relaunch it, it says "Needs Optimization" as if you never ran it before. I dunno what's the point of all those Betas/Release Previews really when this whole OS is a non-ending Beta mess

 

But newer has to be better

 

This does not happen to me with 3 ssd + 3 hdd, i exit the tool, open it again and it shows the last run

 

Yeah try rebooting, it goes back to "Never run"

 

YES YOU ARE RIGHT

well, not really a big problem lol, but it is dumb indeed, how do you mess something that works since windows 7

 

Based on what they produce, I envision a large group of intoxicated male chimpanzees simultaneously attempting to molest a medicine ball.

 

Intel confirms issues with Optane Memory and the Windows 10 May 2020 Update pcworld.com June 5,2020

Intel confirms reports that the Microsoft Windows 10 May 2020 Update is causing compatibility issues with certain types of Optane Memory. Intel published a support document that details steps to fix the issue.

On Friday, an Intel spokesman confirmed that Intel is aware of the issue, and is working with Microsoft on a fix. He told PCWorld that compatibility issues specifically apply to the Intel Optane Memory H10 and the original Optane Memory M10, which debuted in 2017.

It also noted that the bug had been reported to Microsoft as part of the Windows Insider process, but somehow made it into the shipping build. It’s not clear whether the users who are reporting issues with the May 2020 Update and Optane Memory are forcing the update through the Media Creation tool, or are merely requesting the update through the normal Windows Update process.

And why the need push out new major OS update when they know it contains bugs like this? Microsoft even block this OS version from being installed on own hardware. Why not wait ship it when it's ready? Yeah, we talk about Microsoft here!

Bumps on the road to the Win10 version 2004 upgrade askwoody.com June 5th, 2020

I see the same pattern, every time Microsoft releases a new version of Windows. This time’s even more bizarre than usual:

• Microsoft won’t install version 2004 on any of Microsoft’s latest hardware
• The “Update is on its way” message doesn’t make any sense
• Intel-based machines with Optane memory are getting crushed

And there are loads and loads (and loads!) of problem reports

Do yourself a favor. If Windows Update gives you the opportunity to “Download and install” Win10 version 2004, say a prayer for the cannon fodder (we appreciate their problem reports!) and resist the urge to click. There’s nothing in 2004 that you need!!!

Details in Computerworld Woody on Windows.

 

Woody said it. End of discussion. Woody knows.

 

Windows 10 Start Menu promo for Microsoft Edge can't be disabled bleepingcomputer.com | June 6, 2020
Microsoft has recently started to show advertisements for Microsoft Edge every time you search for a competing browser, and there is no way to prevent it.

Windows 10 2004: Laptop or tablet with connected monitor may flicker or go black deskmodder.com | June 6, 2020

The list of known bugs for Windows 10 2004 is long, very long. But does not mean that these errors also occur with everyone. It is precautionary.

Another more specific error has been added to the Microsoft support page. Anyone who has connected an external monitor to a laptop or tablet and has set "Duplicate" using the Windows key + P may experience a problem when drawing in programs or apps such as an office or whiteboard.

Both monitors can flicker or the external monitor goes black. In the Device Manager, the graphics controller shows a yellow triangle. As a workaround, only the laptop or tablet has been able to restart. Microsoft is working on the problem.

 

Best to not use the crappy stock Start menu anyhow. Classic Shell or StartIsBack (my favorite) are both far superior, and they don't support the unwanted nagging advertisements from the Remond Mafia.

 

Yeah, and don't let the new Edge being install on any of your computers. Don't support lackluster.

 

Windows 10 May 2020 Update is causing issues with Drive Optimizer windowslatest.com | June 11, 2020

Yesterday, Microsoft announced that Windows 10 May 2020 Update (version 2004) is rolling out to more users who manually check for the upgrade. The release has been pretty smooth, but some people are complaining that the new update broke Windows 10’s built-in tool to optimize storage drives.

According to user reports and our own tests, Windows 10 May 2020 Update has been shipped with another unacknowledged bug that causes the “Optimize Drives” or “Defragment and Optimize drives” tool to act up.

The bug somehow made it into the shipping build, but Microsoft has already implemented the fix in the preview builds of Windows 10 Manganese update.

.....................................................................................................................................


Latest Windows 10 Bug Breaks USB Printers – Microsoft Says It’s Working on a Fix wccftech.com | June 11, 2020

USB Printer is missing on Windows 10 version 1903 and later (with workaround)
by Martin Brinkmann on June 10, 2020 in Windows - 3 comments
If you run a device with Windows 10 version 1903 or later, e.g. Windows 10 version 2004, and use an USB printer, you may notice that the printer is sometimes missing when......................


---------------------------------------------------------------------------------------
And what is better "put" in an bug that push you into their new mess?


NEWS ANALYSIS
Some Win10 PCs are apparently being upgraded to version 2004 without consent
I’m seeing an increase in the number of people who claim that their Windows 10 version 1903 or 1909 computers were upgraded to version 2004, without warning. The behavior might be due to a bug in the way Win10 handles "Pause Updates"...

I can clearly see Microsoft have spent the time properly during Corona times! Why push it out before 1th summer month when they know this new Joke is full of bugs? And not a long time and we will see the fall edition visit our your computers.

 

@Papusan @Mr. Fox

Tweaking Windows 10 to remove features and lock down your privacy? You're violating Microsoft's copyrights
June 11, 2020
https://betanews.com/2020/06/11/tweaking-windows-10-violating-microsoft-copyright/

 

* DELETE THIS POST * (ninja'ed by Papu!)

 

PAYBACK TIME...
Microsoft is Buying GitHub


https://www.onmsft.com/news/its-official-github-is-now-owned-by-microsoft
“Our vision is to serve every developer on the planet, by being the best place to build software,” said Friedman. “This is a dream opportunity for all of us at GitHub Microsoft, and we couldn’t be more excited to roll up our sleeves and start this next chapter.”

 

What is a day without good/bad news? Sometime there can be an advantage be color blind.


May 2020 Update: Blue/Green Squiggly lines bug reported windowslatest.com |
June 11, 2020

It appears that some Windows 10 users are having trouble with May 2020 Update and F.lux, a popular program that adjusts a display’s colour temperature. Users are reporting that Windows 10’s May 2020 Update is causing Blue/Green Squiggly lines on their secondary monitor.

 

And nothing will change. It looks like they have gone into a private agreement not to like each other


Windows 10 update and Avast bug prevents apps from running windowslatest.com | June 12, 2020

Based on reports, both Windows 10 cumulative update and Avast update are breaking down the apps.

If the problem persists and you don’t use Avast, you can also uninstall Windows 10 cumulative update KB4560960 or KB4557957.

To remove the update, open up the Settings app and then click ‘Update & Security’. From Windows Update pane, click ‘View update history’ then ‘Uninstall updates’ and finally select ‘KB4560960’ if you’ve version 1909 and KB4557957 if you’ve version 2004.

If you use Avast, you’ll need to update the program to the latest version, which resolves the bug, according to the company.

 

Windows 10: program start does not work, Avast fault
Published on June 14, 2020 by Günter Born

​

[ English ] In Windows 10, some users had the problem that certain programs suddenly did not start. Now the cause is known: Security solutions from Avast or AVG prevented these program starts after the June 2020 Windows updates.



Resolution: This issue has been resolved by Avast. This issue only affected devices with certain versions of Avast or AVG applications and was addressed with an update to their respective products. For more information on this, please see Avast's forum post here.

A recent update broke something in this filter that was causing the programs to not launch.

This problem is not the first time it has happened with Avast's software. People have reported this same bug with the Autoreactivator.exe since 2017.

So it is again the combination of a Windows update and third-party software that collide with each other.

.......................................................................................................................................



Windows Update bug triggers driver update loop on Windows 10 windowslatest.com | June 14, 2020

“Windows update keeps trying to install a previous version of Intel UHD Graphics chipset despite the fact that latest drivers are present. The issue appeared after installing May 2020 (v2004) update,” one user noted in the Feedback Hub.

On Twitter, Microsoft’s Windows Dev handle noted that the issue might be caused by the update cache and you should be able to fix it by following these steps:

• Head to Settings > Update & Security > Troubleshoot. In the Troubleshoot page, select Windows Update.

• Select ‘Run the troubleshooter’.

Yeah, easiest way let the users fix their buggy mess.

..................................................................................................................



MICROSOFT, SECURITY
Windows 10 Privacy Settings bug lets users change admin options bleepingcomputer.com 1 June 13, 2020
An "Important" and equally ironic vulnerability, tracked as CVE-2020-1296 was fixed in the Microsoft June 2020 updates that allows privilege escalation in the Windows Diagnostics & Feedback settings app: the annoying privacy setting screen is shown to users when setting up or upgrading Windows.

 

And the fun with the latest and greatest continue.... More of the same. And it will never end!


Windows 10’s latest update bug forces tablet UI on desktop windowslatest.com | June 15, 2020

Windows 10’s June 2020 cumulative update for version 1909/2004 has had its fair share of failings recently and a number of users reported that the patch broke their printers. It looks like there’s another bug in the patch that forces tablet UI and creates extra spacing between icons and folders.

..........................................................................................


Microsoft’s update breaks Fresh Start feature on Windows 10 windowslatest.com | June 15, 2020

Windows 10 needs a fresh start when a system file has been corrupted or the operating system’s gone awry. Luckily, Microsoft has included two tools—Fresh Start and Reset, and Cloud Reset with Windows 10 May 2020 Update....

..............................................................................................


Windows 10 Alert: Defragger bug defrags SSD Drives too often bleepingcomputer.com | June 15, 2020

With the release of Windows 10 version 2004, the Windows Defragger has become a mess as it starts to defrag SSD drives too often, perform trim on non-SSD drives, and forgets when it last optimized a drive....

......................................................................................

And of course the new Chromium browser get same treatment...

Microsoft investigats Autostart bug on the Chromium Edge borncity.com | June 15, 2020Posted on 2020-06-15 by guenni

​

The new Chromium Edge has an exotic bug that causes the browser to autostart. Microsoft has begun investigating this bug and is asking the community for their help.

 

Windows 10 2004: Problems with storage spaces
Published on June 15, 2020 by Günter Born

​

The recently released Windows 10 May 2020 Update (Version 2004) is teeming with bugs. Administrators in the corporate environment who rely on storage spaces should wait until the upgrade. There are problems with storage spaces....

Windows 10 May 2020 Update is causing new issues for Chrome windowslatest.com | Today

Windows 10 is suffering more problems thanks to the faulty May 2020 Update – and this one could be its most annoying problem yet, with users reporting that Google Chrome and a few other.....

Windows 10 version 2004 has yet another nasty undocumented bug, despite being tested for 15 months and serviced for 5 months.

##########################################################

Who will bet on that Win 10 version 2004 will be one of the worst buggy release from Microsoft in history? I'm 100% sure they can surpass this buggy mess!

 

"Recent Windows 10 updates block programs from running"

- Since the release of the Windows 10 1903/1909 KB4535996 and Windows 10 2004 KB4557957 cumulative updates, Windows users have been reporting that they receive errors that programs are missing when they attempt to launch them.

- For example, when trying to launch Microsoft Office applications, like Word, you would receive the following error message: "Windows cannot find 'C:\Program Files (x86)\Microsoft Office\root\Office16\WORD.EXE'. Make sure you typed the name correctly, and then try again."

- ... others have reported having this problem without Avast software being installed.

https://www.bleepingcomputer.com/ne...ndows-10-updates-block-programs-from-running/

---

Avast ye mateys! It's broken with or with out it.

 

I have never seen so many bugs in any build like this. This had a very long beta/preview program going on too!

 

It is been a SAD, SAD drop from where this company once stood. What I don't know is if the population in general knows how bad it is?? For me, it's now 100% Linux all the way!

 

There is zero reason for upgrade to this mess. Maybe around Christmas time or the spring 2021 for those with regular Windows versions. But I expect the buggy problems will continue in same way as with 1903 when 1909 came out from the small patch. We suddenly got two almost identical versions with same problems. No thanks.

 

Storage spaces issues?? I need to go home and turn my Server updates off

 

Why not use the few engineers they still have to fix current versions? Build a new Win 10 version on top of their new released buggy mess will only make the coming OS equal messy! Doomed to fail!


Microsoft announces Windows 10 version 20H2 update windowslatest.com | Today

Microsoft has made it official: Windows 10's next update will now be officially known as Windows 10 version 20H2 and it would be a minor release with a focus on quality improvements... As we noted above, Microsoft hasn’t committed to an official release date for Windows 10 version 20H2 update to the millions of PCs who aren’t in the Insider beta testing program.

About a month after Microsoft began shipping the new and shiny Windows 10 May 2020 Update, the company announced Tuesday that it’s begun shipping the first builds on its next feature release: Windows 10 20H2.

 

It seem's Microsoft is in need for more test machines to help fix their new buggy OS version

Microsoft Begins Force Installing Latest Windows 10 Version 2004 on Some Devices wccftech.com | Today

In an update today, Microsoft has announced that it has started to train its machine learning based process that is used to automatically update devices that are approaching end of service. This means v2004 surprise is coming for those of you still running Windows 10 versions from 2018 and earlier.

[Updated List] And It Begins… All the Windows 10 v2004 Known Issues as Confirmed by Microsoft Itself | Today


--------------------------------------------------------------------------


Windows 10 2004 may break Storage Spaces, avoid using chkdsk bleepingcomputer.com | Today

Microsoft says that users could experience issues using or accessing Storage Spaces configurations on some devices after updating them to Windows 10, version 2004, or Windows Server, version 2004.

No workaround available
While at the moment there is no workaround to prevent these issues from affecting some Storage Spaces configurations after applying the May 2020 Update, users can still access their data by marking them as read-only to continue using them.

 

and now Microsoft will be resuming the offering of "Optional" Win10 updates starting in July 2020 after pausing them last month

"Resuming optional Windows 10 and Windows Server non-security monthly updates"
https://techcommunity.microsoft.com...-and-windows-server-non-security/ba-p/1471429

"Microsoft to resume Windows optional cumulative updates in July" - from Bleepingcomputer
https://www.bleepingcomputer.com/ne...-windows-optional-cumulative-updates-in-july/

and that MS Defragger bug in 2004/20H1 is still there (let's not forget about that, Papusan):
https://www.bleepingcomputer.com/ne...t-defragger-bug-defrags-ssd-drives-too-often/

 

Well that sucked, I just tried to update to the new 2004 version - it appeared automatically in my Windows Updates so I didn't do it manually. I mean I did choose for it to be installed, just I didn't do it manually. Anyway, the update failed and I ended up in a boot loop where it was trying to repair the startup, but it couldn't. Of course I did a Macrium Reflect backup of the small OS partition before I started the update procedure, and I went into a USB booted Macrium Reflect to restore the image of the backed up OS partition. It carried out that restoration sucessfully but then I was stuck in the same boot loop again. So I went into the BIOS and looked at the different boot options and my Sabrent NVMe drive wasn't even listed (which is my OS drive)! So I go into some more boot options and managed to find a kinda obsure part of the BIOS where I could choose whether to use an old redundant boot partition of one of my SSD's that are in there (from another PC) and thankfully also showed the boot partition of my Sabrent NVMe drive - so I selected the latter which brought the Sabrent boot partition up as an option in the main section of the BIOS. I then rebooted and my PC is finally back to normal! I have a feeling that the update to Windows version 2004 would have worked if I had done this last step when it was stuck in the boot loop the first time, but it's still an error in the 2004 update process. As it stands I am still on version 1909 - given my experience I'll be staying on this one until they force me to install version 2004 then! And if they haven't resolved this error in their update process by that point, at least I'll know I can probably get the new update installed by doing that last step I described to select Sabrent boot partition in UEFI BIOS. Windows update process should be messing with my BIOS though. Fail from Microsoft.

EDIT: Actually, it's not fixed, I get an error each time I restart the computer - then if I select "Recovery" it boots fine and is usable until next restart. The "Recovery" process is very quick though, as quick as pressing the button almost. Something wrong though, ideas? I'll update with the error code. Here's a pic of the error code at each startup:

Pressing Esc for recovery works and allows me to boot into the desktop but I have to do this each time I restart the PC, any ideas on how to fix?

 

See if you find something here... Windows 10 May 2020 Update common problems — and the fixes

................................................................................

Windows 10 version 2004 slams into a Storage Spaces brick wall woody on windows | Today
According to official sources, the latest Windows upgrade contains a bug in the Storage Spaces feature. Information, as usual, is sketchy. We have no idea what triggers the bug, or whether rolling back to 1909 will fix it, but .... why is Microsoft still driving this train wreck?

Given the likely severity of the problem, Microsoft should yank version 2004 now, and hope that more people don’t lose their data. It isn't enough to hide behind an upgrade block.

Microsoft shouldn’t have shipped Win10 version 2004. Delaying the ship date is the first item in my list of Five steps Microsoft should take RIGHT NOW to help us through the pandemic, published two months ago. There are no feature upgrades worthy of the term – version 2004 primarily re-arranges the chairs on the deck. In the “tick-tock” new Win10 scheme of version upgrades every six months, this one doesn’t tick. It thuds.

After fives months of testing the final version of Win10 version 2004, we get this.

 

"Microsoft releases cumulative updates to fix Windows 10 print error issues "

- Over the weekend, Microsoft acknowledged a print spooler issue that was caused by last week's Patch Tuesday updates.

- The issue affected all supported versions of Windows, including Windows 8.1 and Windows 10 versions 1507, 1607, 1709, 1803, 1809, 1903, 1909, and 2004.

- Today, the Redmond firm is releasing cumulative updates to fix the issue, but only for some of the affected versions. Versions 1909 and 1903 are getting KB4567512, version 1809 is getting KB4567513, and version 1803 is getting KB4567514. As of right now, there's no solution for Windows 8.1 or Windows 10 versions 1507, 1607, or 2004.

https://www.neowin.net/news/microso...-updates-to-fix-windows-10-print-error-issues

---

If you first break it, fix and fix again.

 

I tried updating to 2004 again (in a bid to resolve the boot issues I described in my previous post) and this time it seems to have worked although it is giving me the option to boot from 2 different locations on startup which is a bit of a pain as it doesn't just load straight to desktop from power on. I think the reason for all these problems I'm having is that it got confused during the installation process because I've got another SSD in the PC that has a boot partition from another computer (a redundant boot partition that I don't use). It might need a reset or clean installation to completely erase this issue, but I'm not doing that yet.

Another thing I've noticed is that it's updated the microcode for my 6700K to CC. I think this is part of the overall 2004 update because all the KB installations are not referring to microcode updates....so there's no way of avoiding the new microcodes if you go version 2004 because it's "built into the core" of the update and is not a seperate KB that can be uninstalled. I suppose I could go the VMWare option to update to change the microcode back to C6, not doing that yet though. Overall disappointing problems and loss of control brought about by Microsoft's Windows 10 ongoing developments and updates.

EDIT: I was able to use msconfig to delete one of the phoney operating systems from the boot menu....as a result the boot menu screen no longer appears on startup, so problem is fixed.

 

Solutions for that as well. Delete it!

http://forum.notebookreview.com/thr...r1-bios-unlocked.802440/page-29#post-11017238

 

@Papusan @Mr. Fox @Spartan @Vasudev @jclausius +++++++ everyone who I missed.

Get ready to be nuked, New M$ Defender is now looking into your BIOS flash chips. Perhaps soon, we won't be able to use Custom sBIOS like Prema or unlocked sBIOS like my AW17 because it has been tampered with or some BS signature checking filth drama. Orwellian dystopia is near, with Kernel Level Anti cheats running in wild barring us to run with DSE disabled (EAC does this on Halo MCC) and what not for crappy fad games (Valorant) where they run the whole time and god forbid who knows what they a people are fine. This is next level.


UEFI scanner brings Microsoft Defender ATP protection to a new level

Check those Secure Core PC's I bet all of them are eligible to be Blacklist.

It constantly keeps on reading your BIOS ROM through the motherboard chipset SPI interface. And any change to the BIOS registers will be definitely red flagged (see below) and also blocking any changes to the HW, I don't know, could be wrong but I get Throttlestop to mind first. And adding any signature verification filth it becomes even more nasty, makes me remember Nvidia Falcon. As there's a picture showing how NVRAM threat was found.

Subverting people to think secure boot is really great and how M$ takes care of them well, pathetic. This new Draconian Orwellian nightmare is not going to end any time soon, I think this is just beginning, very sad how OS has become now esp with Windows. I really miss the era of XP and Windows 7.

A question, can we remove Defender from LTSC ? IIRC it became an integral part of OS and removing it will cause issues.

 

I have nothing to worry about. Windows Defender is the first thing I disable, or better yet...

Windows 10 Disable Defender Script

Place the $OEM$ Folder in the sources folder on the ISO/Windows 10 USB Install Disk, Windows Defender will be disabled from the get-go when you install Windows

LTSC has Windows Defender.

I first disable it from within the app itself, then immediately disable it from Group Policy Editor otherwise it will re-enable itself upon reboot. Then I disable it once more using Winaero Tweaker and finally I disable its background services which are usually locked:

Enable/Disable Windows Defender Services

 

Excellent, thanks! Seems like a real easy fix for microcode to revert to using the BIOS stored version on the motherboard.

EDIT: done, returned to C6 microcode, took a short while to work out how to change ownership of files.

 

https://www.zdnet.com/article/micro..._content=FeedBurner+user+view#ftag=RSSbaffb68

 

I think it will not affect us at the moment!
I think in MS Docs, there must be a driver (DCH) which can transparently read through SPI. I think WD broke my sister's laptop BIOS after forced upgrade to 1709. I bet 90% of PCs are not supported since OEM must make driver that can communicate to OS which rarely OEM makes since they use generic UEFI component driver.
Then again, BGA Jokebooks aka public jokebooks and not Business laptops which comes with dTPM doesn't rely on SoT(Silicon of Trust) keychain and runs on discrete security chip. Ever since Intel security exploits, I disabled fTPM since I don't trust Intel Silicon anymore.

I Hope WD doesn't remove firmware junkware included in my Secure BIOS made by Dell as Malware. Haha....

 

For all of you who is on Win 1809 Home and Pro. It's about time close the doors. Win 10 1809 is still valid until Nov. 2020. There is no need for the moment to jump on the new buggy and flawed Windows 10 May 2020 Update.

Windows 10 V1809: Auto Update to Version 2004 has begun?
Posted on 2020-06-18 by guenni

​

It appears that Microsoft has now begun preparations to force systems running Windows 10 version 1809 Home and Pro to update to the Windows 10 May 2020 Update (version 2004).

 

We all know how detrimental UWP has become for Windows platform and Personal Computing as a whole. The best part was it failed horribly due the lack of developer support and MS hamfisted approach to the problem that didn't exist except to take over the Windows and hijack it for their own agenda.

Well they abandoned the Store, but the cancer still lives on fellas...and now it has been reanimated to haunt us forever.

Microsoft’s Project Reunion: Win32 and UWP unite

A quick google on the MSIX takes to MS page,

And then what is MSIX

Say goodbye to any modifications or such which has all those above mandatory restrictions like a noose.

From this link

Funny they mention no longer locked, lmao UWP garbage is only for Windows 10 WaaS, zero ownership while the machine which I'm running is using Win32, same browser can be installed onto 2004 crappy Win10 SAC update or 2019 LTSC release or Win7 SP1 as well, that's called no lock to a particular version of Windows. Not the fake Windows called Win10.

They do mention that Webview2 works for all Windows versions, but remember this is just a PWA and .NET, not the native apps from what I see here, so their BS of selling snake oil of this no Windows version lock is lame, as they want everyone to move to that PWA in the name of more user base (Always OL, Internet connection based just hit the above Webview2 link and see that scale from Reach ---- Power)

Wait you might think it won't fly, yeah it might not fly but look at this link, their GitHub page

Telemetry built into the damned API itself. Next level tracking haha.

And on a closing note ... these are big changes that will be coming to the Windows for the foreseeable future as we see, I expect many changes, Chrome is already starting to use the Edge's Segment Heap from UWP + Win32, Project Reunion for it's BS memory hog but that's the first step, M$ wanted Google to sell their garbage UWP+ Win32, with the world's most popular browser and first software that many install this process is very quick, in exchange they supply the tinder through Edge becoming a Chrome Blink engine clone spybox.

A storm is coming only time will show us if this will fail or not, I sincerely hope it falters and leaves the Win32 alone FFS for the sake of concept of "PC"

 

Looks like Apple took this idea and baked into Mac OS XI. UI looks like Win 10.

 

"Microsoft says June 2020 updates break Outlook for some users"

- Microsoft says in a support document recently published that Outlook will fail to start for some users, automatically displaying an error prompting the users to repair some inbox files.

- ...all users who have updated Outlook to version 2005 Build 12827.20268 or higher will see an error prompt saying that "Something is wrong with one of your data files and Outlook needs to close. Outlook might be able to fix your file. Click OK to run the Inbox Repair Tool."

- ...known issue as being caused by the June 2020 updates

- No fix yet, workaround available

https://www.bleepingcomputer.com/ne...ne-2020-updates-break-outlook-for-some-users/

---

We know what a new round of Windows updates means... New bugs to watch and new work-arounds to deploy

 

Windows 737 Max latest news:

"Microsoft confirmed yet another bug for recent versions of its Windows 10 operating system. The bug may lead to forced reboots"

https://www.ghacks.net/2020/06/24/add-a-forced-reboot-bug-to-the-list-of-recent-windows-10-issues/

 

The "Defer Feature Updates" option is removed in the May 2020 Update (v2004)

Windows 10 V2004: Defer Feature Update removed
https://borncity.com/win/2020/06/25/windows-10-v2004-defer-feature-update-removed/

ZDNet - Microsoft removes manual deferrals from Windows Update by IT pros 'to prevent confusion'
https://www.zdnet.com/article/micro...ndows-update-by-it-pros-to-prevent-confusion/

only way to defer feature updates in 2004 is to use the Group Policy (gpedit.msc)

 

"Windows 10 June 2020 updates cause forced reboots, LSASS crashes"

- Microsoft acknowledged a new known issue leading to Local Security Authority Subsystem Service (LSASS) critical system process crashes and forced reboots on some Windows 10 devices.

https://www.bleepingcomputer.com/ne...0-updates-cause-forced-reboots-lsass-crashes/

---

More details on the issue in @6730b's last post.