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: Most helpful
  1. Anonymous
    2021-10-20T10:56:23+00:00

    hi have a problem in updating to the latest insider build while restatrting my lap went off and i tried turining it on and the install failed after that

    i again tried downloading the update but i am getting error and showing as windows 10 insider can you help with this

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-10-19T17:00:35+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

    Hi suat.cini,

    I still see intermittent flickering on file explorer Right Click menu with 22478.1012. Also sometimes the delete of a file appears to do nothing even if the file is actually deleted, to refresh I have to close and reopen file explorer.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-10-19T14:40:48+00:00

    I have a simple question here. Do the dev channel preview builds (which I'm currently using) include the fixes that are also in the stable pipeline? I'm asking because I use an AMD processor and was wondering if the builds we're getting also fix the issues that were present with the CPU. Also, has anyone else had the issue of ICUE not displaying any devices at all with this new build?

    Was this answer helpful?

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