Windows 10: cant update to preview 10041 error 0x80070003

the iso dosent work ether, i get a setup couldn't start properly please reboot pc and try again

 

I was able to fix the problem. This is what worked for me:

I did a repair install of Build 9926 using the ISO file.
I installed all Windows Updates.
I was then able to install Build 10041 using Windows update, without a problem.
I would recommend creating a hard drive image prior to this, using your favorite disk imaging software.
That way if something goes wrong, you can always revert to the system you had.

 

Just tried to update with the new 10041 ISO posted by MS and it failed on the first reboot also.

 

Please let members know how you installed Windows 10

Native, as primary OS

Dual Boot
What OS is the primary?
Running a native VHD boot?

Virtual machine
Hyper-V
VMware player (version#)
Oracle VMbox (version#
Host OS ?

Thanks

FYI: The TP download page has moved !

9926 Download Windows 10 Technical Preview ISO - Microsoft Windows 10042 Download Windows 10 Technical Preview - Microsoft Windows

 

Thank you for the links. With the bugs I am finding in Build 10041, it was not worth the hassle to upgrade.

 

I'm getting error 0x80246017 when trying to update.

After all I'll pass this build.

Will I be able to update to the next preview directly from 9926?

*Smile

 

No quotes so unsure who you mean.

Dual boot on separate hard drives installed from ISO build 9841(IIRC) with W7 as main and default OS.

May try a repair install of 9926 but from what I've read maybe this build isn't worth the trouble.

 

Tried the repair from 8826, actually refresh is what it's called. From 9926, it want media which could be caused from earlier BSODs. During which it rebooted several times. Finished but wiped out about twenty apps, no settings retained but kept the Documents folder intact.

I changed the default OS in msconfig to my W7 OS. Restored an 9926 image but right now dual-boot is hosed as it booted right into W7 right after the restore with no selection option, pressing F12, selecting W10 and it boots into W7! Oh well.....been here before!

 

Thanks wptski - it was a general call for anyone in this thread to provide more information.

I'm guessing that the 9841 install has been updated though the preview build update process? Or are you tryin to go directly from 9841 to 10041?

Give MS the feedback from your update experience - that will help in the long run.

Then ...
The best advice I can offer anyone in this thread is to do a clean install to whatever you boot Win10 using the 10041 ISO
Windows 10 Technical Preview ISO March Update - Microsof Windows


I've read a lot of members saying that the issues in a particular PB release aren't worth the trouble to install.
That's the point of a PB release - it's not production code.

I guess there are two types of Insiders
1) Test drivers - just taking it for a spin
and
2) Techno Geeks - don't mind development code and watching how issues get resolved.
The only thing that will stop me from installing a PB release is: If the state of the PB release prevents me from installing it..
This happened with 10.041 through the update channel. It took me many hours to get it installed (I boot to VHD and the install said You can't update a VHD). I tried to do the ESD to ISO thing, but the ESD kept getting removed before I could grab it. Third time's the charm, got the ESD and created the ISO.

I could have waited a few more days to get the ISO from the Insider Pgm, but ... I'm a Techno Geek *Tongue

Best of luck to everyone.

Bill
.

 

Yes, it's been updated from 9841 to the present 9926. I know I can do a clean install but I'm one that doesn't do that for every build. Updating builds is closer to real life use than a clean install. I may do a clean install but right now I don't relish the thought of installing twenty apps. I've never did a clean install on my 4+ year old W7 machine, only one repair install after few months. This refresh/repair is only my second since W95.

BTW: W10TP build 9926 is booting again, it was just boot delay timer.

 

Thanks for amplifying how you are managing the updates.

I completely understand - and appreciate your diligence to the 'normal' process.

I manage my installs by downloading any favorite apps I use on a regular basis (gfx & text editors, A/V player, office suite, and my trusted toolbox utilities). I don't install EVERY application on every build - only the 'essential' apps.

I do test all apps every few installs, but only to see if they operate - you're right ... that takes too much work to do every time *Wink

It's good to see other members managing the TP in different ways. I learn form the issues that show up on their machines, but not on my machine ... I also learn what might be causing an issue on my machine that way. It's a really great community on the DM forums.

It sounds as though you are a very good representative of a normal Windows user ... on the other hand, I'm a techno geek and by definition break a lot of things by mucking around in system files. Then I have to figure out how to fix what I broke *Tongue

Anywayyyyyy, it's good to hear that your machine is back up and running on 9926.

Thanks again for the update,

Bill
.

 

Since I restored, just for kicks, I downloaded 10041 again not expecting it to update. Be darn if it started to install. I wasn't expecting and didn't uninstall my AV which in the past halted the install. It stopped for this, I paused it but maybe should have clicked on Uninstall. Short version, it didn't restart, I restored yet again and am downloading 10041 again. I'll uninstall my AV first this time. Watch it error out like it did a dozen times before! *Confused

 

I can't update to preview 10041: Error 0x80246017

Windows TP 9926 is updated
I have reverted registry keys back to their original values

What else can I do?
Any idea?

*Sad

 

is Build 10041 really so bad? is there a list of bugs i can see?

 

i still cant for the life of me install this Build 10041 even with there fresh iso from there website! its like microsoft doset want mt to try!

can someone tell me where the windows 10 setup keeps its fail logs because "something has happened" dosent explain Shit microsoft!*Mad

is this it?

setupact.log & setuperr.log in

$windows.~bt\Sources\Panther