Replies

The option @CraigS26 is referring to is in each individual browser’s settings not Windows and, for most Chromium-based browsers, it’s not a cogwheel but a button!

The default setting for most browsers is to automatically update installed extensions but it’s possible to force a manual update check as follows:

Right-click the extension icon on the right-hand side of the menu and select Manage Extensions and you should now see something similar to this at the top of the list of installed extensions.

Click it to initiate an update check.

BTW, if you don’t see it, turn ON developer mode.

My Aunt, Uncle and Nephew all have Spectrum e-mail addresses.

I just checked and they’re all still working just fine.

Just FYI, I had to use their webmail link (https://webmail.spectrum.net) to reactive my Uncle’s account because it’d hadn’t been used for more than 90 days (actually +10 years since he’s never used it) but it came right back to life with 196 unread messages in it!

Optane memory (also known as 3D XPoint) was a special type of non-volatile memory that significantly sped up everything the OS did.

It was available from Intel Apr 2016 thru Jan 2021 (they closed the Optane division in Jul 2022) and required a special Intel chipset and motherboard ports (a non-standard type of M2 port) to function.

It was an available option from most PC manufacturers for a while but, because SSD’s gave very similar speed increases at a much cheaper price, never really achieved a high percentage of market penetration.

If your PC has it, it should be mentioned in the user manual for your PC and will be shown somewhere in the BIOS settings.

Because of how it works (it moves parts of the OS into itself) it’d present a problem for any and all backup S/W unless it’s been specifically designed to deal with that bit of strangeness!

BTW, Intel Optane memory shouldn’t be confused with Intel’s Optane SSD’s – which are still available and compatible with any motherboard just like other SSD’s.

2 users thanked author for this post.

Cybertooth, Tech Hiker

Glad to hear you finally got it sorted out.

Yes, everything on the destination drive will be replaced with the backed up contents of the source drive.

Just FYI, that’s normal when restoring an image backup, regardless of which particular backup S/W is being used.

BTW, according to your screenshot, the backup image was Basic GPT Hard Disk 0 but the destination is Basic GPT Hard Disk 3.

Normally, unless you’re replacing a particular drive with a “new/different” drive, you’d want to restore the backup to the same drive it originally came from.

If you actually do want to restore the backup to a different drive, you’re go to go.

If not, you should change the destination drive to the Basic GPT Hard Disk 0 the backup originally came from.

RetiredGeek wrote:

This is a Dell laptop and it uses Optaine memory for something and I’m pretty sure that is the culprit.

100% correct!

To properly backup/restore a PC that’s using Optane memory with Macrium, you have to disable Optane before backing up or or it won’t actually be a full image backup because the main part of the OS has been moved into the Optane memory (that’s how it accomplishes it’s magic of “speeding up” the OS.)

For more details see Optane m10 and Macrium Reflect Free thread over on the Intel Community forum (especially this post).

BTW, the other solution is to do exactly what you did, mount the image, and then copy the relevant parts back to the original drive.

3 users thanked author for this post.

windbg, satrow, RetiredGeek

@Tex265,

The problem is that David Xanatos, the creator of wumgr, has never provided a complete guide/help/FAQs for his program nor details about exactly what each of the various options actually do so, since day one of it’s initial release, each individual user has pretty much had to figure it all out via trial & error.

The closest thing to such a guide I’ve run across is the Guide to Using WuMgr for Windows 10 Updates thread here on AskWoody; and even it’s not complete because no one, except David Xanatos, really knows what all the options do!

All those “quick overviews” you’ve seen are because that’s how those users got it to work for them and they weren’t interested it the how or why questions you’re asking just that it worked.

BTW, JMHO, but asking others to be your guinea pig probably isn’t the best way to get meaningful responses.

2 users thanked author for this post.

Cybertooth, opti1

Ed Willers wrote:

The note in Updates that “Some setting are managed by your organization” is still there. I would like to make that go away so I can run updates normally.

As I noted above in my post #2757337, Having even one update setting value different that Window’s defaults will cause the *Some setting are managed by your organization message to appear on the Updates screen.

In your case, it’s being displayed because you have the following Group Policies set to Windows 10 22H2.

Target release version for feature updates
Source: Administrator
Type: Group Policy

Target product version for feature updates
Source: Administrator
Type: Group Policy

And, as @PKCano pointed out above, if you remove it, the message will disappear but then you’d lose control over how/when updates are applied (i.e. all new updates would get automatically installed!)

1 user thanked author for this post.

opti1

Group Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select the target Feature Update version

The specific registry entries it sets are:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
TargetReleaseVersion
TargetReleaseVersionInfo

TargetReleaseVersion & TargetReleaseVersionInfo are simple text values as follows:

TargetReleaseVersion = Windows 10 or Windows 11

TargetReleaseVersionInfo = 21H2 or 22H2 for Windows 10, 23H2 or 24H2 for Windows 11

1 user thanked author for this post.

Ed Willers

As Susan pointed out, if you used InControl.exe to set your preferred version to 21H2, you’ll need to change it to 22H2.

You do this by pressing the Release Control button, change the Release from 21H2 to 22H2, and then press the Take Control button.

If that’s not applicable to your situation, then click the View configured update policies text displayed right below the *Some setting are managed by your organization message and it’ll display all the Policies set on your device and you can change whichever one is causing update not to finish.

If you’re not sure which one it is, post a list of them here and we should be able to help.

BTW, have you/did you ever use wumgr.exe?

If so, there’s some options that can cause this sort of problem if they were set and, since it’s not an installed problem, deleting it won’t restore them to their default values.

Just FYI for everyone who reads this thread…

Having even one update setting value different that Window’s defaults will cause the *Some setting are managed by your organization message to appear on the Updates screen!

2 users thanked author for this post.

opti1, Elly

I pretty much follow the same procedure as @Paul except, instead of separate folders, I use a single folder with separate zipped archives for each type of document.

BTW, I started using spaces in filename after Microsoft changed from FAT to NTFS that allowed filenames longer than 8 characters (Windows XP) and I’ve never experienced any problems with doing so except for my own “self-inflicted” issues!

i.e. “forgetting” to use quotes around filenames that include spaces when referencing them from a batch file or script.

I do occasionally use special symbols (-, +, _, &, etc.) but normally try to avoid them as they can cause problems when using a batch file or script!

Me neither.

Bearing in mind, except for Insider Builds, Windows 10 never required a MS account for activation and not all users will be using a MS account to login to their PC; exactly how would they “legally” obtain the address of every Windows 10 user in order to e-mail them such a notice?

I could understand such a notice being integrated into the month updates in order to reach every Windows 10 user, but via e-mail… that seems extremely unlikely to me!

1 user thanked author for this post.

LHiggins

Mark wrote:

I dislike downloading from NVIDIA because a lot of garbage comes with the driver.

You can avoid that by downloading the update directly from https://www.nvidia.com/en-us/geforce/drivers/ and making the following selections when installing it.

3 users thanked author for this post.

Alex5723, Cybertooth, satrow

RetiredGeek wrote:

Verified DirecX 12 with the following PowerShell Script:

Much simpler to run dxdiag.exe

1 user thanked author for this post.

RetiredGeek

Successfully installed the March Windows 10 22H2 updates on 2 PC’s with no issues.

No sign of the new Outlook and the BlockedOobeUpdaters = [“MS_OUTLOOK”] registry setting is still there.

One interesting item caught my eye when searching my OS drive to see if the new Outlook files were downloaded or not.

I found a folder that was created on 02/13/25 (same day I installed the Feb CU that was “suppose” to install the new Outlook).

C:\ProgramData\USOPrivate\ExpeditedAppRegistrations\MS_Outlook

That contains a file called updater_Outlook.json with these contents.

{
    "PFN": "Microsoft.OutlookForWindows_8wekyb3d8bbwe",
    "OEMName": "MS",
    "UpdaterName": "Outlook",
    "RegistrationVersion": 1,
    "Source": "Store",
    "ProductId": "9NRX63209R7B",
    "Scenario": "Acquisition",
    "Priority": 50,
    "HonorDeprovisioning": true,
    "MaxRetryCount": 5,
    "TimeoutDurationInMinutes": 15,
    "SkipIfPresent": true
}

I “assume” this was intended to be part of the new Outlook install process that never happened because I have the registry block in place to prevent it.

Anyone else have this file?

Can I delete it without causing problems; such as suddenly finding the new Outlook was installed instead of blocked?

My first PC was an Apple II+ purchased back in 1979 with the 64 KB language card and used cassette tapes for saving/restoring programs.

And yes, it was KB not MB (ah, the good old days of 6502 8 bit computing!)

I stayed with Apple up thru the Apple IIgs and then, because that never offered any sort of upgrade path from the II family to the Mac family, I finally switch to Windows 3.11 on a Gateway laptop.