Weird stuff going on. Just got this warning on the screen, hit start to run winver to include in the comment but everything froze. Luckily, I was able to take a screenshot with Win + PrtSc Got it again after a restart before I could do anything and now I get it on every restart. 😒 Does anybody knows how to stop it?

Weird stuff going on. Just got this warning on the screen, hit start to run winver to include in the comment but everything froze. Luckily, I was able to take a screenshot with Win + PrtSc Got it again after a restart before I could do anything and now I get it on every restart. 😒 Does anybody knows how to stop it? It sure looks weird; I have not seen that message yet. 🤣🤣🤣 Yes, the expiration date is 9/15/2022, but that is quite normal with dev builds. And your screen shows the current date correctly, 7/16/2022. 😎😎 Some old links about the issue: Build of windows will expire soon - Microsoft Community Fix: 'Windows Will Expire Soon' Popup on Windows 11 - Appuals.com

Hi fg001, thank you for the valuable info. Perhaps this is the reason that creating an ISO from UUP dump takes such a long time to actually build

Hi Sibro, I finally think I isolated the experimental feature that was causing the 0xc0000005 when booting in Safe mode. Today MS disabled 4 different features and enabled a new one, and the problem was no longer occurring. So, I just reenabled those one at the time and found the culprit. 😎 It is listed as: AugmentedEntryPointBadging: 36718398 I have no idea about what it is or does, but without it the bug is gone. 🤣🤣🤣🤣 I reproduced the same 0xc0000005 error by enabling the same above feature on two other boxes that never failed before. 🤐 The other 3 features have something to do with Widgets behavior and the changes that we have seen recently. The added one they enabled is listed as: LiteWhiteNTH: 33355279 Whatever that does? 🤣 Thanks MS, for not explaining anything they do under the covers. 🤐🤐🤐🤐🤐 https://aka.ms/AAhgxeo

RS-Prerelease Build 25158 + ISO is out to Dev Channel

CrazyKats 19,760 Volunteer Moderator

Live in W.U.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Anonymous

2022-07-17T04:06:41+00:00

Weird stuff going on.

Just got this warning on the screen, hit start to run winver to include in the comment but everything froze.

Luckily, I was able to take a screenshot with Win + PrtSc

Got it again after a restart before I could do anything and now I get it on every restart. 😒

Does anybody knows how to stop it?
Was this answer helpful?

0 comments No comments
Anonymous

2022-07-17T05:34:02+00:00

Weird stuff going on.

Just got this warning on the screen, hit start to run winver to include in the comment but everything froze.

Luckily, I was able to take a screenshot with Win + PrtSc

Got it again after a restart before I could do anything and now I get it on every restart. 😒

Does anybody knows how to stop it?

It sure looks weird; I have not seen that message yet. 🤣🤣🤣

Yes, the expiration date is 9/15/2022, but that is quite normal with dev builds.

And your screen shows the current date correctly, 7/16/2022. 😎😎

Some old links about the issue:

Build of windows will expire soon - Microsoft Community

Fix: 'Windows Will Expire Soon' Popup on Windows 11 - Appuals.com
Was this answer helpful?

0 comments No comments
Anonymous

2022-07-17T07:29:27+00:00

Hi fg001, thank you for the valuable info. Perhaps this is the reason that creating an ISO from UUP dump takes such a long time to actually build
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2022-07-17T23:24:07+00:00

Hi Sibro,

I finally think I isolated the experimental feature that was causing the 0xc0000005 when booting in Safe mode.

Today MS disabled 4 different features and enabled a new one, and the problem was no longer occurring.

So, I just reenabled those one at the time and found the culprit. 😎

It is listed as:

AugmentedEntryPointBadging: 36718398

I have no idea about what it is or does, but without it the bug is gone. 🤣🤣🤣🤣

I reproduced the same 0xc0000005 error by enabling the same above feature on two other boxes that never failed before. 🤐

The other 3 features have something to do with Widgets behavior and the changes that we have seen recently.

The added one they enabled is listed as:

LiteWhiteNTH: 33355279

Whatever that does? 🤣

Thanks MS, for not explaining anything they do under the covers. 🤐🤐🤐🤐🤐

https://aka.ms/AAhgxeo
Was this answer helpful?

0 comments No comments