Blocking Chromium Edge

Microsoft is slowly rolling out the Edge replacement called Chromium Edge. “ChrEdge”, as some call it, will install on top of the Edge that came with Windows 10 [Microsoft calls it Legacy Edge].

Chromium Edge is based on the open source Chromium browser which was originally developed by Google. So Chromium Edge is using a variation of the Google Chrome browser engine but with its own unique differences.

For the few who have used the Legacy Edge, the interface hasn’t changed too much except where it applies Chromium changes. Chromium Edge will replace the Legacy Edge. So settings will be migrated. Unsure if you can roll back. Never tried.

Chromium Edge will also be available for Windows 8.1 and surprisingly Windows 7 – which has no support from Microsoft. Server versions of the client versions of Windows can also install Chromium Edge.

Note that it doesn’t directly replace Internet Explorer – Internet Explorer will not be removed or disabled.

If you wish to block Chromium Edge from getting installed, apply the following registry fix:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate]
“DoNotUpdateToEdgeWithChromium”=dword:00000001

Note: Unsure if the blocker will work on Windows 7 or Windows 8.1 or server equivalents. Haven’t tested.

Note: You must be at Windows 10 v1803 or newer to use this blocker.

To unblock, set DoNotUpdateToEdgeWithChromium to 0. Or kill the value all together.

 

Changed to Feature Updates in Windows 10 v2004

Feature Updates are those huge twice a year updates that are part of Windows 10. In most cases, these updates can take at least 45 minutes.

Professional, Education and Enterprise editions – up until v1909 – were allowed to modify when Windows can check for these Feature Updates. You were able to defer the update by a year. [Especially good since some recent Feature Updates have had issues.]

As of v2004 [“May 2020 Update”], this has changed. You can only change the way Feature Updates are checked by using the Group Policy Editor or the registry.

To modify, open the Group Policy Editor and follow the path Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Feature Updates are received.

By registry to disable:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
“TargetReleaseVersion”=dword:00000000

By registry to enable:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
“TargetReleaseVersion”=dword:00000001
“TargetReleaseVersionInfo”=”2004”

Replace 2004 by the appropriate version that you want to scan for [obviously greater than the version you currently are using].

If you have the Home version, this information can’t be used.

As usual, use this information at your own risk.

 

Issues with June 2020 Windows updates

Seems bugs in Windows updates never end. Reports that the June updates for Windows versions v1903, v1909 and v2004 [KB4560960 & KB4557957] may cause the following:

  • Can’t print to a Ricoh, Canon or Brother printers [doesn’t specify if laser or inkjet] or if you can, the connection isn’t stable.
  • Micro-HDMI port stops working.
  • Windows doesn’t recognize a second monitor.

It seems that Microsoft has quite a bit of work to clean up.

Growing issues with Windows 10 May 2020 Update

It seems the list of problems keep on growing and growing for Windows 10 May 2020 Update [a.k.a. v2004]. The strangest part of this mess is that this feature updates was actually available for months. In addition, at least one issue [the Optane memory] was discovered 2+ months ago but ignored.

Here’s a list [some may not have been reported]:

  • DISM reports incorrect status.
  • Variable refresh rate may not work on PCs with Intel GPU.
  • Performance issues.
  • Intel Optane memory issue.
  • Bluetooth connectivity issues with Realtek drivers.
  • External displays might go black if you try to draw in apps such as Office Word or Whiteboard.
  • Conexant ISST audio drivers are causing BSOD.
  • Plugging or unplugging a Thunderbolt dock causes BSOD.
  • Other random BSOD including when you resume the system from sleep or hibernate state on a Lenovo laptop.
  • Synaptics ThinkPad UltraNav driver issue.
  • Random reboots on systems with Always On, Always Connected features.
  • Yellow warning mark on the disk drive.
  • Mouse input may not work in apps and games using GameInput Redistributable.
  • Boot issues when aksfridge.sys or aksdf.sys is present.
  • Nvidia GPU driver version 358.00 or older causes BSOD.
  • Fresh start allows Windows 10 users to clean up Windows installation without removing personal files.

You can see the status here. Not a good sign when the site shows no resolved issues…

 

 

 

What’s new in Windows 10 v2004

So what is new in Windows 10 v2004 [a.k.a. 20H1, a.k.a. May 2020 Update, a.k.a. …]?

Developers got their hands on build 19041.208 today with Microsoft expected to roll it out to users starting May 28th. The most compatible systems [such as newer systems] will see the update first, followed by everyone else… Eventually.

Here is a partial list of updated features:

  • GPU temperature monitoring comes to Task Manager
  • Disk type [i.e. SSD, PATA] now visible in Task Manager Performance tab
  • Quick Event Create from the Taskbar
  • File explorer search is now powered by Windows Search
  • Go passwordless with Microsoft accounts
  • Adding Mouse Cursor speed to Settings
  • Improving the Optional Features page in Settings
  • Introducing a new Reset this PC option–Cloud Download – you can use the local installation or download Windows 10 from a Microsoft server
  • Updated notifications options
  • New Bluetooth pairing experience
  • Automatic restart for Desktop & UWP apps to reduce sign-in time
  • Search indexer tweaks to handle excessive disk usage – indexing will stop or throttle under any of 9 options are reached [i.e. game mode is on, high CPU usage, high disk usage, etc.]
  • New throttling options for Windows update downloads
  • New Cortana features & experiences – does anyone care?
  • Redesigned Network Status page

Note: Unsure if fixed yet, early testers experienced some issues with Bluetooth devices.

At this time, the next major update will be released probably in October or most likely in November. It is expected to be similar to last fall’s 2019 Fall Update – where you didn’t need to have this huge installation.

Miscellaneous computer tips – Volume 14

Transferring a distribution list

Say you are using Outlook and you are the head of a team. You have accumulated a distribution list of your own contacts. Now someone else is taking over the team and would like the distribution list. How would you do it?

  1. Open the distribution list in Outlook.
  2. In the File menu, select Save As and save the distribution list as a .MSG file. Save it where you can find it.
  3. Send the file to the new team leader.
  4. In Outlook for the new team leader, save the file received.
  5. Open the Contacts folder.
  6. Drag and drop the .MSG file into the Contacts folder.

Enable notifications in Outlook

Those running Windows 10 may find that they are not receiving any audio notification when a new Email arrives even though the audio notification is enabled. To fix the issue, use the following registry fix:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
@=””
“C:\\Program Files\\Microsoft Office\\Office16\\outlook.exe”=”~ WIN7RTM”

You need to update the path above to match where is outlook.exe located on your system.

How to enable images in signed encrypted or signed Emails in Outlook

in the rare case where you may get a signed or encrypted Emails in Outlook, you may not be able to see the images.

To fix the issue, [depending on the version of Outlook]:

  1. Go to the File menu, then Options.
  2. Click on Trust Center on the left and then Trust Center Settings on the right.
  3. Click on Automatic Download on the left.
  4. Uncheck the box Don’t download pictures in encrypted or signed HTML email messages on the right.
  5. Click on OK to close.

Windows 10 May Update Delayed

Shocker!

While no official dates given, it looks like Windows 10 May Update [a.k.a. v2004] will be released this month but barely.

Originally, the release 19041.207 was to be released this past April 28th with a public release on My 12th.

Microsoft decided after build 19041.207 was cleared that they wanted one more fix.

So May 12th will be the release date – but when released to developers. Barring a setback, the release to the public will be May 28th.

With that extra time, don’t be surprised if there will still be another build before the 12th.

There are at least 3 outstanding issues:

  • Windows Mixed Reality
  • DISM (Deployment Image Servicing and Management) – The tool is used to repair corruption on systems running the May 2020 Update but does not always report the correct status.
  • IME (Input Method Editor) – Probably affects non-Roman languages primarily

 

Issues with Windows 10 v1903 & v1909 update

Those who have installed the cumulative update for Windows 10 v1903 and v1909 [kb4549951] are reporting a variety of issues. Included in them are:

WiFi, Bluetooth, crashes, system performance [memory and CPU], external monitor to be used, headphone issues, and Chromium Edge and Google Chrome resolving site issues.

Some have complained even about losing data.

And this is assuming the update can be installed as some can’t even get it to install

I noticed the slowness in resolving in Chromium Edge.

Microsoft is looking into the issue.

 

The Next Windows 10 Feature Update

The next Windows 10 feature update will be released [to technical people and OEM companies] within the next 2 weeks.

It will be called Windows 10 May 2020 Update with build 19041. It also goes under the name Windows 10 v2004 or 20H1 and the code name Vibranium.

Microsoft will begin to roll out the update to consumers in early May [probably May 12th] with the most highly compatible systems getting notified first. These would mostly be recently released systems.

FYI, the update technically has been finalized since December.

Microsoft update KB4524244 pulled

In an ever growing list of Microsoft updates that have had problems with, add KB4524244 to the list.

The update was designed to address “an issue in which a third-party Unified Extensible Firmware Interface (UEFI) boot manager might expose UEFI-enabled computers to a security vulnerability.”

The update has since caused freezing, booting and installation issues.

KB4524244 gives you ways of removing the update.