Replies

Dear Susan,

Solved!  Thank you very much!  And thank you for reading CVEs whose significance I would not understand.

On my relatively new PC, I decided that instead of partitioning the 1TB drive , I would create a subdirectory C:\@Data for everything on my earlier D: drive.  Then I used Visual Subst from NTWind to substitute D: for C:\@Data  permanently.

After reading your reply, I opened the Properties windows of both LNK files, and changed D:\ to C:\@Data\  in the Target: and Start in: fields.  When I rebooted, the problem was fixed — no more warnings.

I then checked the other LNK files that I had written in both Start-ups,  and found that I had used C:\@Data\  instead of D:\ , so that is why they did not also trigger warnings.

There have been just a couple of earlier issues where I had to change paths from D:\ to C:\@Data\ to make things work.  I now have another such issue — and I am kicking myself for forgetting about the substitute drive and writing my post.

I have just posted the following feedback on the Microsoft instruction webpage, detailing the error in the Registry path on my desktop PC:

I have Windows 11 Pro 22H2 Build 22621.1848
The Registry path given above for W11 22H2 opens as far as
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies
This path contains one subfolder ‘Hardware’. There is no subfolder ‘Microsoft’.

There was no room to add how disgraceful it is to be asking non-techies like me to edit the Registry.

Is this a new all-time low for Microsoft, or am I just a non-techie who can’t read instructions?  I’m beginning to think that their Windows platform is no longer safe for me to use.

3 users thanked author for this post.

Specialist17, Mark, geekdom

Dear Susan,

First, my apologies.  I can’t find whatever article I was reading about KB4023057 adding to LCPE the ability to stay on Windows 10 (top box) and 21H1 (second box), and from your and Alex5723’s comments, I must have misread something.  The woes of not being a techie!

KB5005101 that you mention is listed in ‘Other Updates’ on the desktop where the new LGPE box was added, but not on the notebook where the LGPE box was not added.  This confirms what you have said in your most recent post.  (I did search various places in LGPE  on the notebook for the relevant entry , but I cannot find anything.)

On the notebook, I tried to uninstall KB4023057, but as I reported, `The update KB4023057 is listed on Windows Update –> View Update History as ‘Successfully installed’, but it is NOT listed in Control Panel –> Uninstall a Program –> View installed updates.’  So the update seems to have been half-installed?

I read  https://www.makeuseof.com/manually-uninstall-windows-10-updates  and ran the command  wmic qfe list brief /format:table  in an elevated CMD window.  The resulting list appeared to be the same as the Control Panel list. (Although it gave all the KB numbers instead of only a few of them, whereas the Control Panel list had other details that the CMD list did not have — why is Microsoft being so unsystematic and confusing?)

KB4023057 is mentioned on the Notebook’s Windows Update list, but not on the Control Panel  or CMD lists, even though the CMD list contains other updates at the same time.

The notebook with the problem is running 21H1, 10.0.19043.1165, while the desktop without the problem is 21H1,  10.0.19043.1202, and Windows Update reports that both are up to date.  Yet the notebook is Windows-11-capable according to ByteJams, but the desktop is not — for various reasons.

I don’t understand.  Microsoft is one of the largest and wealthiest companies in the world, and Windows is their main product, yet it is totally impossible for an experienced, well-qualified user with some coding ability to follow their procedures or understand the strange turgid language that they use on their webpages.  Anyway, now that you have told me that Windows 11 will not get pushed, I will take you advice and do nothing.  Thank you very much for your time.

My post above on the ‘Just a moment . . .’ blue screen after boot (Issue 1) seems to have been a false alarm.

The system was becoming increasingly sluggish, so I uninstalled several very large pieces of software that I had over-enthusiastically installed for future projects.  After a couple of reboots, the sluggishness has gone, and so too has ‘Just a moment . . .’

I have uninstalled NordVPN for other reasons, so I reckon ignore Issue 2 also.  Apologies.

Two issues that each occurred immediately after installing a September update.  I eventually installed them all, perhaps unwisely, because of fear about insecurities in Windows.  I have 64-bit Windows 10 Pro 2004, now fully updated, on a desktop.

ISSUE 1:  I installed KB4576478 on 2020-09-10 (.NET Framework 3.5 and 4.8), because it seemed wise to update .NET.  Ever since, I get the blue window ‘Just a moment . . .’ after every login.  It stays there for nearly four minutes, then every is normal.   I have not the slightest idea how to get rid of it, but it is really annoying me and slowing me down.

ISSUE 2:  I installed KB4571756 on 2020-09-13 (the big cumulative update for 2004), in the forlorn hope that this might possibly fix the ‘Just a moment . . .’ problem.  Ever since, I cannot use NordLynx with NordVPN — NordLynx uses WireGuard.  No real worries here, because Nord’s OpenVPN works with no problems, both TCP and UDP, but why the issue with Wireguard?

I can only report.  I leave it to experts to diagnose what caused these issues — and hopefully how I can removed the wretched blue window ‘Just a moment . . .’.