Recent content by DennyZenny

I recognized the same thing in my unsupported system's 22H2 to 23H2 migration. Glad to hear 25H2 will be a similar deal especially since we won't need a huge platform shift to get those bigger features user-facing features. Hopefully it'll be like that time when we got relatively big changes...

You'll need an in-place upgrade or clean install to get 24H2.

To hopefully get the thread back on track, I've done some research and it looks like OP is not alone. There have actually been several people (Reddit, answers.microsoft.com, DPReview, Borncity) experiencing issues with 24H2 deactivating their Windows installation as you can see below. Windows...

I would if I could, but I don't have any working Windows PCs at the moment.

Might be a perfect time to report the issue using the feedback hub?

feels like something is happening! :unsure:Almost like they're starting to ramp this up after years of stagnation.

Not really, just because the build number hasn't been updated doesn't mean the code itself hasn't been changed. The lack of updates to the build number is just in case an older program has a habit of checking the kernel version number.

my guess on why it hasn't received text yet is localization.

Dont forget to report these issues to the feedback hub

Successfully installed. No issues so far, but also not new features rolled out to my system yet.

I have noticed this as well and am contemplating filing feedback on this through the Feedback Hub.

I've actually had relatively niche issues fixed via the Feedback Hub. It was in insider builds though.

You can also contact Jen Gentlemen via Reddit (u/jenmsft) or on Twitter. She mostly handles feedback for WIndows.

Thanks for the reminder! I definitely need to remember to back-up my phone now that I'm not using iCloud anymore.

I actually like this workaround alot better than bypassNRO. The command is much easier for me to remember, and I don't have to worry about mixing backslashes and forward slashes.