New bug in Build 23493.1000, fails when trying to boot in Safe Mode, F4 or F5 get this same error, and if I try to login the screen start flashing with the second screen shot and never shows any desktop icon or taskbar. Confirmed on a VMware VM but I don't get the error. 🤷♂️ Upvoted.

New bug in Build 23493.1000, fails when trying to boot in Safe Mode, F4 or F5 get this same error, and if I try to login the screen start flashing with the second screen shot and never shows any desktop icon or taskbar. https://aka.ms/AAlif5t

@fg2001 Yes you are correct I am still missing RunAsPPLBoot. 🤷♂️ I was attempting to wait for MS to apply their correction, rather than use one of yours (ours), but it has been a long wait and I am vacillating on which way to go. It's 5 months now since it started and MS appear very uninterested. After telling us it is important not to use any other workaround as they are working on a fix? Davy. Added RunAsPPLBoot Rebooted twice However there appears to be more than just a missing DWORD because I still have no Local Security Account Protection. However MS say that they are working on the problem and will have a fix soon ........ ? 😴 Davy. Two separate issues: RunAsPPLBoot was eliminating the reboot message for LSA when it was available in settings. With the latest kb5007651 they removed the LSA settings option completely, in public Build, R.P. . Beta and Dev channels, still available in Canary with the same Security update version. 🤐🤷♂️ Build 23493.1000: LSA option is gone from Settings in Dev Build too. 🤷♂️

My feedback has been updated. They are looking into it, but with no offical response.

@fg2001 Yes you are correct I am still missing RunAsPPLBoot. 🤷♂️ I was attempting to wait for MS to apply their correction, rather than use one of yours (ours), but it has been a long wait and I am vacillating on which way to go. It's 5 months now since it started and MS appear very uninterested. After telling us it is important not to use any other workaround as they are working on a fix? Davy. Added RunAsPPLBoot Rebooted twice However there appears to be more than just a missing DWORD because I still have no Local Security Account Protection. However MS say that they are working on the problem and will have a fix soon ........ ? 😴 Davy.

Build 23493 is out to Dev Channel Insiders

CrazyKats 19,680 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

61 answers

Anonymous

2023-07-10T23:42:42+00:00

New bug in Build 23493.1000, fails when trying to boot in Safe Mode, F4 or F5 get this same error, and if I try to login the screen start flashing with the second screen shot and never shows any desktop icon or taskbar.

Confirmed on a VMware VM but I don't get the error. 🤷‍♂️

Upvoted.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-07-10T23:18:36+00:00

New bug in Build 23493.1000, fails when trying to boot in Safe Mode, F4 or F5 get this same error, and if I try to login the screen start flashing with the second screen shot and never shows any desktop icon or taskbar.

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

0 comments No comments
Anonymous

2023-07-07T17:32:41+00:00

@fg2001

Yes you are correct I am still missing RunAsPPLBoot. 🤷‍♂️

I was attempting to wait for MS to apply their correction, rather than use one of yours (ours), but it has been a long wait and I am vacillating on which way to go. It's 5 months now since it started and MS appear very uninterested. After telling us it is important not to use any other workaround as they are working on a fix?

Davy.

Added RunAsPPLBoot

Rebooted twice

However there appears to be more than just a missing DWORD because I still have no Local Security Account Protection.

However MS say that they are working on the problem and will have a fix soon ........ ? 😴

Davy.

Two separate issues:

RunAsPPLBoot was eliminating the reboot message for LSA when it was available in settings.

With the latest kb5007651 they removed the LSA settings option completely, in public Build, R.P. . Beta and Dev channels, still available in Canary with the same Security update version. 🤐🤷‍♂️

Build 23493.1000:

LSA option is gone from Settings in Dev Build too. 🤷‍♂️
Was this answer helpful?

0 comments No comments
Paul Chou 1,471 Reputation points

2023-07-07T12:32:08+00:00

My feedback has been updated. They are looking into it, but with no offical response.
Was this answer helpful?

0 comments No comments
Anonymous

2023-07-07T10:20:00+00:00

@fg2001

Yes you are correct I am still missing RunAsPPLBoot. 🤷‍♂️

I was attempting to wait for MS to apply their correction, rather than use one of yours (ours), but it has been a long wait and I am vacillating on which way to go. It's 5 months now since it started and MS appear very uninterested. After telling us it is important not to use any other workaround as they are working on a fix?

Davy.

Added RunAsPPLBoot

Rebooted twice

However there appears to be more than just a missing DWORD because I still have no Local Security Account Protection.

However MS say that they are working on the problem and will have a fix soon ........ ? 😴

Davy.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments