Forum Discussion
insider preview 17074 not working
Same as the last three updates - gets stuck at the windows logo with no spinning dots. Have to power off and revert to 17035.
error log:
2018-01-13 12:30:32, Error MOUPG Finalize: Error reading narrator reg key: [0x80070002]
2018-01-13 12:33:00, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2018-01-13 12:33:32, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{52776FBF-403C-49cc-b7cb-dd557f36096A} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2018-01-13 12:33:50, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #144468# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })
[gle=0x80004005]
2018-01-13 12:36:56, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get preferred homegroup with hr=0x80070490
There are issues w/nVidia drivers (I have Ti1050 OC) in terms of how they load in Windows 10 RS3/4 Builds---after you install latest nVidia driver (most of you 64-bit, I bet). 'disable' driver in 'devices' so you get a 22 code....re-boot machine, go back into Windows but do not 'enable' card---power off, unplug power, press start button machine so power is not still there, and is used....then, plug back in power supply, re-boot, 'enable' card, and you should be good.
If you cannot get in latest Insider build, back-door it with a dual-boot (comes in handy) and use Unlocker via other Windows-based OS (on different partition) to delete the nVidia .inf file in windows/system32/driverstore/respository...the files are 'protected' but Unlocker will allow you to delete /inf...then re-boot, and then re-install nVidia driver but 'disable' it, and go thru above....took me a bit to nail this one...hope it helps some of you.
69 Replies
- Jim DanekeCopper Contributor
I had so many GSOD that I gave up on Windows until I removed Acronis.
No more problems.- Anonymous
Thanks for the information. BTW, Have you tried fully testing the Fall Creator's Update. I have found version 1709 to still be buggy in testing. I suggest version 1703 or less to all my clients. I fix computers in the States.
- Jim DanekeCopper Contributor
I run 17083. Works fine now that Acronis is gone.
- Holger BatenCopper Contributor
My Windows insider preview version 17074.1002 freezes (SYSTEM_SERVICE_EXCEPTION) my Surface 3 Pro only when I login with my (long used) MS Account. I can login and work with another user which was already on the maschine.
Even elevating this other working user did not work, every time I entered the password of the admin user the system crashed.
Now when I removed ntuser.dat.log1 and ntuser.dat.log2 from the "bad" users profile, I was able to login again. But then the profile cannot be saved any more.
So how can I make the ntuser.dat.logx files 17074 compatible again?
- Anonymous
My understanding is that Microsoft is working on an update to your issue Holger.
- Anonymous
Just a thought, in the future can we have error logs as a file chosen instead of just copying and pasting the entire error log - it would make the discussions flow more smoothly - just a thought
- Mitchell MorrisCopper Contributor
Justing too tired to try anything more. I've tried everything even manually reinstalling my graphics driver after performing a complete and total reset, whereas I made sure that nothing extra was installed. This was the last step I took after following just about every other recommendation I could find on the net with no resolve. The dots just keep spinning after the first automatic restart.
I think the latest update just plain has something wrong with Alienware Area 51R-2, running AMD. And Windows, you might want to look into it.BTW, I don't think 17074.0002 fixed it.
- Mark RobertsCopper Contributor
Just a quick heads-up on 17074 - I have it installed but when I tried to print I got errors saying there was a problem with my Printer Setup.
I have an OKI C301DN.. It works fine from other connected PCs but not the 17074 version pc.
I have been onto OKI and this is a new error from their point of view. All drivers deleted and reinstalled. Gone back to generic driver from OKI - still no joy.
Also my previous 'loudspeaker' default also suddenly changed without anything being done by me.
Something is not quite right.
Also a lot of CPU being used by Telemetry Services?
Will report back if this is resolved
- Michael BertelsenCopper Contributor
I got the same problem with a Dell C3765dnf on 1704. It worked until this update...
- Jim DanekeCopper Contributor
Pitiful. I can't get my Gigabyte to a stable build. I have to keep stopping updates every week after I live through another failed upgrade.
Thanks Microsoft. Time for Linux.
- Paul WarrenIron ContributorHi all, I had this with the previous two fast ring builds. The (Temp) fix for me was to disable virtualisation in BIOS/UEFI. Jason Howard confirmed to me that MS will be doing a fix very soon - Hopefully in the next build
- Paul WarrenIron ContributorFYI - if you had to disable virtualisation, the insider team have just released a patch - https://blogs.windows.com/windowsexperience/2018/01/11/announcing-windows-10-insider-preview-build-17074-pc/amp/?__twitter_impression=true
- Robert KelleyCopper Contributor
Sadly, I've had same problem with my Acer TC-780, and the advice to disable virtualization is pointless as it's hard-coded ON in the BIOS for Acer desktops. So I've been stuck now for the past month rolling back updates.
- Ed TittelCopper ContributorMy business partner and co-author Kari Finn just spent 4 days getting 17074 to work on his Acer laptop. The secret turned out to require 2 special ingredients: 1. turn off secure boot before beginning the upgrade process, don't turn back on until Win10 activates 2. use slmgr to remove the product key for your install before upgrading, then it will activate automatically when installation completes HTH, --Ed--
- leonidas crouchBrass Contributor
I don't have secure boot as an option.
- leonidas crouchBrass Contributor
not sure what else to do now - this is the third update since 17035 that does not work. My laptop upgrade fine which only adds to the frustration!
I've tried all suggestions and still the same happens.
I know it's a 'beta' but I'm surprised how many people are having this issue and it hasn't been sorted as yet....
- Mark GravesCopper Contributor
Update to Preview 17074.1000 fails for me too. Dell Inspiron 15 7000 Gaming (with Nidia GTX 1050 Ti)
- Александр КовалевскийCopper ContributorАналогичная модель, с такой же проблемой. dell inspiron 7000
- Michael MaloneCopper Contributor
Windows 10 Insider Preview Build 17074 is not working, stuck at the windows logo with no spinning dots and no USB activity during clean install. Display Adapter is a nVidia GeForce 310.
- R SharpCopper Contributor
There are issues w/nVidia drivers (I have Ti1050 OC) in terms of how they load in Windows 10 RS3/4 Builds---after you install latest nVidia driver (most of you 64-bit, I bet). 'disable' driver in 'devices' so you get a 22 code....re-boot machine, go back into Windows but do not 'enable' card---power off, unplug power, press start button machine so power is not still there, and is used....then, plug back in power supply, re-boot, 'enable' card, and you should be good.
If you cannot get in latest Insider build, back-door it with a dual-boot (comes in handy) and use Unlocker via other Windows-based OS (on different partition) to delete the nVidia .inf file in windows/system32/driverstore/respository...the files are 'protected' but Unlocker will allow you to delete /inf...then re-boot, and then re-install nVidia driver but 'disable' it, and go thru above....took me a bit to nail this one...hope it helps some of you.
- leonidas crouchBrass Contributor
do i do this BEFORE I install the insider preview?
- Chad SparksCopper Contributor
Same thing here.