RS-Prerelease Build 22478.1012 KB 5007328 is out to Dev Channel Updated

CrazyKats 19,330 Reputation points Volunteer Moderator
2021-10-14T17:00:10+00:00

Live in W.U.

The .1012 update is just a test of the servicing pipeline,

no fixes.

Windows Insider program | Program announcements and registration | Communications and announcements

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 No comments

182 answers

Sort by: Newest
  1. Anonymous
    2021-10-19T07:45:08+00:00

    Hi suat.cini,

    I tried all different combinations of updates from previous builds and even a clean install of 22478.1012 with default settings and I always ended up with the same bugs.

    Hi fg2001,

    I also have a bug: flickering ( it's actually crashing ) right-click context menu on files and folders. If I hover over on files/folders for 2-3 seconds before right-clicking, flickering/crashing never happens. This issue has never been addressed on build 22000.xxxx iterations. Now I have stopped complaining. Previously, I filed in several feedback hub reports.

    Host M/C: Legacy Windows 11 build 22000.282 > Flickering/crashing happens

    Guest M/C: UEFI Windows 11 build 22478.1012 > No flickering/no crashing happens

    So I assume flickering/crashing right-click context menu on files/folders resolved for builds in 224xx iterations.

    Regards

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-10-19T06:43:45+00:00

    Hi suat.cini,

    I tried all different combinations of updates from previous builds and even a clean install of 22478.1012 with default settings and I always ended up with the same bugs.

    I was not doing anything special, I have the problem on 3 different machines and in my case it is reproduceable very consistently when the setting is on for

    "Use my sign-in info to automatically finish setting up after an update".

    When I turn that off all the failing machines run just fine without those problems.

    There are already many other user that reported the same problems, but I have no idea why some users have the problem and other users don't. That seems a pretty common situation with most MS problems. 🤔

    Clearly there must be something different that causes the different behavior, but we don't know what yet.

    The only common thing I've seen in my cases is that the failure is not showing on the first login after the install, but fails consistently after that, following every new restart.

    Try a clean install of 22478, that failed too on my machines, but I don't run VM.

    Was this answer helpful?

    0 comments No comments
  3. 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

  4. Anonymous
    2021-10-19T05:08:43+00:00

    Hi.

    I have the same setting on "Use my sign-in info to automatically finish setting up after an update".

    My build is 22478.1012 which is an update over 22471, which was a clean-install.

    This is an Hyper-V VM 2nd gen on a non-compliant hardware host machine.

    Everything runs super fast. Task Manager opens up fast and all tabs are full of info. I can open admin Windows Terminal. UAC comes forward instantly.

    Hope the information is useful.

    If there is anything I must do to reproduce the bug, please let me know. Perhaps I can do it.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-10-19T03:47:45+00:00

    Hi fg,

    Well, if is not because of updating via ISO or WU, then it could be anything in between.

    Don't spend too much time on it, let them figure it out.

    @Sibro.o,

    This is my last test with the MS Account and then I'm done, there is definitely a bug in build 22478, I'm sure they can reproduce it in the lab, there are way too many users that got these same bugs 🤢.

    Edit:

    As I expected, got the same results with MS Account.

    Was this answer helpful?

    0 comments No comments