Announcing Windows 10 Insider Preview Build 14332 for PC and Mobile Insider
-
I appreciate everyone letting me vent in silence a few pages back. Thanks...I needed the space...
I've been trying to troubleshoot my problems since Microsoft is not being much help, and it seems that in 14316 even though it's up and running with only a few overt bugs evident, I have some component store corruption in the build that I cannot fix. Here's what I've done:
1) sfc /scannow says everything is as it should be--no corruption detected.
2) DISM xxx/scan-health says that I have "repairable" component store corruption
3) DISM xxx/restore-health runs but fails at 96.2% every time, citing a remote procedure call error.
4) Per a Microsoft employee's suggestion in another thread I stopped the the Windows search .svc and tried restore-health again--but with the same result.
5) I made my own .iso from the 14316 .esd, and did an in-place upgrade, which should have been the same as a repair reinstall, and I was hopeful but DISM still says the component store corruption is there but "repairable"--so no gain accomplished.
I really, really do not want to do a clean install since I have a lot installed--but besides that, I want to test the way Microsoft intended I test, and I gather that is with upgrades, mostly, since official .isos are few and far between (which is why I wish that Microsoft would release an .iso for every test build, but that's neither here nor there.)
Anyone have any ideas? Here's the appropriate DISM log entry...
DISM DISM Package Manager: PID=5832 TID=5024 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)
2016-04-29 14:57:30, Error DISM DISM Package Manager: PID=5832 TID=5024 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800706be)
2016-04-29 14:57:30, Error DISM DISM Package Manager: PID=5832 TID=5024 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800706be)
2016-04-29 14:57:30, Error DISM DISM Package Manager: PID=5832 TID=5024 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)
2016-04-29 14:57:30, Info DISM DISM Package Manager: PID=5832 TID=5024 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-04-29 14:57:30, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE
Here's what the .cbs log says:
2016-04-29 14:57:30, Info CBS ASSERT: Assertion failed in onecore\base\cbs\util\inc\CbsArray.h(607)
Index out of bound.
2016-04-29 14:57:30, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800706be]
Last edited by waltc; 29 Apr 2016 at 14:08.
-
-
I would group it with the "few overt bugs", and if your system is not crashing every time you want to use it, and generally works OK, try and put the component store to the back of your mind.
It will be soon enough that a newer build will totally replace the component store and all the other bits of the OS.
Ever since my wife's car was bumped in the supermarket car park, the "Frost alarm" goes off just after starting up the engine. We have not had any skidding or other low temperature traction problems, especially during the summer, despite the regular warning!
-
I would group it with the "few overt bugs", and if your system is not crashing every time you want to use it, and generally works OK, try and put the component store to the back of your mind.
It will be soon enough that a newer build will totally replace the component store and all the other bits of the OS.
Ever since my wife's car was bumped in the supermarket car park, the "Frost alarm" goes off just after starting up the engine. We have not had any skidding or other low temperature traction problems, especially during the summer, despite the regular warning!
I'm sure that's what I'll do, but if there is indeed some corruption there, that *might* be the reason both 14328 and 14332 can only install with the UEFI secure-boot function turned off, and why when I do get them installed that the desktops are simply too buggy to be of any use to me... Ah, well, that's life in beta-land, I suppose. Back to waiting for the next build...
-
Something I have never seen or experienced, never even heard about it happened today: Installing 14332 PRO x64 EN-GB on a spare old laptop, totally wiped and empty HDD, booting from install media (flash drive), I got BSOD maybe 5 seconds after starting the laptop, even before this dialog was shown:I've never seen BSOD to happen at that point, only seconds after booting from install media, with no OS installed on system!
BSOD, the new one with the QR code remained only a few seconds, machine rebooted, gave the same second time, again a reboot and this time installation started normally and I had no issues in installing and setting up Windows.
-
-
You could go back to the latest General Release by selecting Stop Insider Preview Builds in Settings>Update and security>Windows Insider Program. That should roll you back to GR, keeping all your apps and data. Then, grab your 14316 ISO, mount it and run setup.exe to do an in-place upgrade. ....
Hi, thanks for your reply.
But in 14328, I can't cancel Insider builds completely, only stop them for 1-5 days.
Well I did this for 5 days, what should happen now?
There is also a Link to (sorry German only):
stop-receiving-builds
But this website doesn't reflect the recent builds and eventually suggests to download a "restore image"
I will download this image now and keep you informed how it continues...
-
That was what I ran into on the second desktop here when normally it would have each new build ready to go on. I am starting to suspect that isn't any glitch but a prefix seen on the 328 build since there wasn't going to be enough time between that and now the 332 only days apart!
The main hasn't seen as many builds overall having stuck with the TH2 which was passed on the second case while that one was shutdown for a month. The main then missed the 14257 while the second case did better one ahead when re-enabling the Insider builds on the main to replace the buggy TH2! This time however it was the second case that was the last and two VMs removed and replaced by two new ones.
Kari has an odd one there for sure since the few BSODs or Blue Screen Specials now being seen(BSS ) with MS changing the looks of that have only been seen once the build is already on or on one occasion the update stalled forcing a hard boot on for the 328 that happened on the second desktop.
-
Hi, thanks for your reply.
But in 14328, I can't cancel Insider builds completely, only stop them for 1-5 days.
Well I did this for 5 days, what should happen now?
There is also a Link to (sorry German only):
stop-receiving-builds
But this website doesn't reflect the recent builds and eventually suggests to download a "restore image"
I will download this image now and keep you informed how it continues...
This selection is not available?
-
This selection is not available?
It is, but it leads you to a website, where you can only dl a six months old standard TH build (General release)
But no chance to keep data and settings, when trying to "downgrade"...
Seems the only chance to keep everything, is to wait for a better working Insider preview...
-
That would be 5 months not 6 at the moment and I saw the 3 days and 5 days options available here but only on the second case when the 332 didn't arrive. I had to hit the Start button which then changed to the Fix me button in the Windows Insider Program section at the bottom under Developers where you now find the Slow-Fast option which was moved out from the Advanced options under Updates. On the main you see the account information, option to stop builds, and the Fast-Slow options there never having seen this come up at all.
-
-
I sure hope there's a new build soon..
I got this glitch during install of 14332 (see the GFX anomaly onscreen) - it froze at this point:
- after about 20 mins of inactivity, I hit the restart button..
- sorry 'bout the screenie, but I'm just too frazzled to rotate it
- AMD graphics have been completely haywire ever since..
- 90% of webpages won't load correctly..
- Fallout4 and many of the latest games wont function correctly
- Quantum Break fails to run at all, as do several Steam titles
- I've given my hardware a good once over and there aren't any faults that I can see
- I have to assume a buggy install of 14332 is the culprit