Manual install 24H2 - only 1 odd problem so far

My 23H2 system never got 24H2 via standard Windows update, even though I've got the "Get updates as soon as possible" option enabled. So I decided to install 24H2 myself, and did that by picking Option 1 from this web page: Download Windows 11.

I expected to have some problems because my system has a few configuration quirks, but the whole process went very smoothly and completed in about 10 minutes (maybe 7?) This surprised me because the odd things in my configuration are

1. Wireless keyboard attached via USB dongle
2. Wireless trackball attached via BlueTooth dongle
3. Dual monitors -primary is 4K landscape and secondary is 2160x4850 portrait, but the secondary it physically attached to the first port on my video card, and the primary is attached to the 2nd port. This typically confuses Windows when rebooting, and always causes BIOS to be displayed 90 degrees from normal via the first video card port
4. C:\Windows\Temp has a Junction Link pointing to Temp on a separate internal SSD drive
5. I sometimes use the legacy Notepad app, so I have it installed in it's own directory on the same SSD as Temp.

#5 is the only one that has caused a problem so far. If I now try to create a new TXT file I get the initial shortcut just fine, but when I try to open it I get this error message:

I've never seen that before and have no idea what it means or what to do about it. The only thing that works is clicking OK, which closes the dialog. But there is no way to enter any data into the text file. If I right-click on the shortcut this message appears:

Obviously I need to do something about this, but I don't use plain text files that much so I'm not going to let this push me back to 23H2. I expect it won't be too hard to find a solution.

Please watch this video. It worked perfectly for me.
Like you, my PC did not get the 24H2 Update offered through Windows Update.

I followed the directions in this video, and it went flawlessly. It took a while, maybe an hour or so total (maybe more)?

How to upgrade an existing Windows 11 installation on unsupported hardware that is on version 23H2, 22H2 or even older, to the latest version of Windows 11, 24H2.

Upgrade to Windows 11 24H2 from Windows 11 23H2, 22H2 or older on Unsupported Hardware

I hope this helps you out

Whoops, sorry that's an odd text file issue I don't have an answer for!

I haven't seen that happen to anyone before.

I would start by riunning the batch file at the bottom of this first post:

There are also other things you can try. Is it only the Notepad App that is giving you this error?

Look in One Drive and see if it's been captured there.

Also right clicking on your desk top doesn't give you the short cut you made for a New Text Document? You can use the new notepad for that.

For the first time I was offered 24H2 via Widows Update today. I made a quick back up and gave it the ok to install. Took a while but it finally installed without any obvious problems. SFC /scannow was error free, however when I did "Dism.exe /online /Cleanup-Image /StartComponentCleanup" it eventually failed. I seem to remember that mentioned a while ago?, don't know if there was a fix or not. The version that was installed was 10.0.27703.1006, Winver shows 24H2 26100.2894. Hoping that it behaves in the near future!

Well...I forgot something. Awhile ago I did an in-place update and had no problems, except after doing the update booting failed because the BCD file was messed up. So I had to runt the Macrium "FIx boot problem" routine to fix that. But I had forgotten that last part - and just had to do it again. Fortunately it worked OK again.

I found a set of registry tweaks that supposedly install and de-install the original Notepad. I ran the installer and rebooted - that's when I remembered I needed to fix the BCD file. But after doing that, and rebooting again, the problem with Notepad still exists. So I'll do some more work on that tomorrow.

Another problem I just noticed - 24H2 put back a 674 MB Recovery partition on my boot drive, and left 2.77 GB unallocated after that. A couple of months ago I went through the process of fixing that - so I'll have to go back and find the postings here that I followed to do that.

"It's always somehting"