Kitz Forum

Computer Software => Windows 10 => Topic started by: Chrysalis on September 01, 2015, 02:31:25 AM

Title: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 02:31:25 AM
well it gets worse.

build 10532 available.
it downloads.
it does its preparation.
it reboots

Then the update screen appears, its the same screen as when updating from windows 7, so the feature updates = upgrade entire OS again including reinstalling drivers, so that bugged out process is repeated on feature updates.

Well I was watching it on the copying files stage, then at about 30% the system just rebooted, after it booted again, it said "restoring previous version of windows".

So it failed but I have absolutely no idea why, because the whole process is dumbed down with no reason given to the end user.

By luck I found an error code stored in the registry.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 02:58:05 AM
And even more ..... :D

http://www.theregister.co.uk/2015/08/28/new_windows_10_insider_build_10532_released_but_microsoft_silent_on_bugfixes/ (http://www.theregister.co.uk/2015/08/28/new_windows_10_insider_build_10532_released_but_microsoft_silent_on_bugfixes/)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 03:01:40 AM
75+ Million people running Beta software that snoops on everything you do.

Could not make it up.  :o :D

MS have truly gone to the Dark side.  >:D >:D

Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 03:16:47 AM
updated post with pic.

its a complete farce really. LOL

you can see is 2 rollbacks as I tried it twice.

That error code I think but is only a think from some googling seems to be bootloader related, very bizarre given I have already managed to get windows 10 installed.

My working theory is at the moment, I have confused the installer/upgrader by adding some more hdd's.

As since installation I added 3 hdd's ro access data on them and also test some FreeBSD stuff on two of the hdd's which have zfs on them, but the ssd with win10 on has not been modified at all by FreeBSD.

If I have to disconnect these hdd's (not trivial in this case, and even moving the case out of its tight area isnt trivial either),everytime to do a build update its a joke.

Aardvark the snooping on my test rig wont yield much :) just me googling how to fix their problems. :)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 03:29:41 AM
From the googling I have done that code has always been related to hardware incompatibilities even on older versions of Windows.

The newest win10 one is as follows:

http://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/camera-not-working-with-windows-10/e751f177-0795-4624-829d-59f15420e26d (http://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/camera-not-working-with-windows-10/e751f177-0795-4624-829d-59f15420e26d)

HP one:
http://h30434.www3.hp.com/t5/Desktop-Audio-Video-Monitors/Win-10-update-error-0x8007001f-install-fail-of-IDT-High/td-p/5175364 (http://h30434.www3.hp.com/t5/Desktop-Audio-Video-Monitors/Win-10-update-error-0x8007001f-install-fail-of-IDT-High/td-p/5175364)

Beta software ...... runs today then broken tomorrow by a MS update, might work again the day after. (Roller-coaster :yay: ) :(
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 03:54:02 AM
yeah my hardware is incompatible thats why it already runs build 10240 LOL.

I disabled the drives in the bios but windows still detects them, I am not going to bother disconnecting them.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 04:02:49 AM
I did disable the 2 drives in device manager also but it still fails.

Going to bed now but tomorrow (or rather later today) I wil try disabling the 3rd hdd in bios and device manager then try it again.

As for the hardware its all mainstream.

intel i5 750
asus motherboard
nvidia gtx 460
no soundcard
intel gigabit pci-e nic

all of which have current working drivers on build 10240.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 07:05:33 AM
The codes you get out of 'random' crashes of Windows Updates are always confusing (read as random).
I have spent untold amounts of time looking up codes which often do not exists anywhere you look on the internet.
(Even MS help often takes you to another code all together ..... or can't find it !)

It couldn't be because the hardware has changed ..... could it ? ........ (Are MS that bad at writing code ?  :no: :no: :no: Surely )

Could it be MS 'snooperry' (new word :D) cannot cope with not being able to read zfs ?
(Nice Filesystem by the way  ... I use it under Solaris 11.1/11.2 with Napp-it on top for cifs/smb access.)

Worse case you need to do the update on a minimal setup then connect the rest of the kit and let the rest of the updates, if any, run.
(Pain in the neck but might work as the update is incremental. Seen it work when there are a lot of updates and MS trips over itself doing a 'Big' update. ???)

Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 03:37:49 PM
the only hardware change is the 3 added hdd's. also the hdd's are on the intel controller, so no complex 3rd party controllers used (all disabled in bios).

Its a known problem that when installing microsoft operating systems its best to have the only boot device in place otherwise it gets confused, but once installed reconnect the other storage devices.

Now whether or not thats the issue here I dont know but I have tried a few more things today all failing, always stops at 61% copying files then reboots and restores build 10240.

and yeah zfs is a brilliant filesystem.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 06:58:12 PM
ok got a bit more info, I made an iso from the downloaded file for the update and tried to install via the iso.
Fails in same spot however after the reboot from recover, I was prompted with this screen.

I have dragged my heavy pc onto the table the monitor is on, so I could take the side off easily and see if I can disconnect any hdd's easily, I disconnected the two zfs drives ready for another attempt.  In the process tho I managed to break one of my usb ports, the usb stick still plugged in must have got jammed against the sofa as is a tight spot.  The stick came out with part of the usb port attached to it, the stick I think is undamaged tho but that port is now no good for use, dont know yet if neighboring port still ok. (is usb port front of case not on motherboard).
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 07:16:04 PM
From a Reddit Thread try this Windows Update Troubleshooter (For Win 7 but said it worked anyway]
http://windows.microsoft.com/en-ca/windows7/open-the-windows-update-troubleshooter (http://windows.microsoft.com/en-ca/windows7/open-the-windows-update-troubleshooter)

Reddit:
https://www.reddit.com/r/techsupport/comments/3fb4ob/we_couldnt_install_windows_10_0xc1900101_0x20006/ (https://www.reddit.com/r/techsupport/comments/3fb4ob/we_couldnt_install_windows_10_0xc1900101_0x20006/)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 08:12:40 PM
can confirm without all the extra hdd's is the same.

Not much else to try now I guess without waiting to see if they release a newer version that fixes it.

If I remove any other hardware it wont function, and yep I found that reddit url, is 68 gig free on the ssd, I did also run a disk cleanup to remove the old windows 7 files which made an extra 11 gig but still fails in same place.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 08:52:28 PM
@Chrysalis
With MS's new Data Slurp mentality .... they know you have a problem so a fix should be winging it way as we speak.   >:D  :lol: [Tin Hat mode on]

So that's what it is for !!!!!  :doh:

Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 01, 2015, 10:20:21 PM
I am lost for words how buggy this OS is and the PR mess they got with the privacy issues.

I have to think back quite a long way for when microsoft had such a broken install process.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 01, 2015, 10:37:33 PM
It really is Beta.
No Joke ..... it is .... end of.

MS Tests all its tricks on the 'dumb' Home users. ( and brave SME's)
Get the OS to a workable state then rolls it out to the Corporate Customers (if any are stupid enough to use it after reading all the tales of Horror.)

I wonder how many Corporate users are going to be lost ?

I cannot think of anything this bad ..... not even Windows ME !
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 02, 2015, 03:20:06 PM
Well an update report, a guy with the same issue (but in his case trying to upgrade to win10 from win7), said he googled someone removing hidden volume devices to fix it, so I tried that, I had over 15 hidden generc volume's in device manager, it didnt fix it but the fail point moved to 58%, interesting.  I then removed some hidden sound devices in device manager which said it couldnt detect them on the system, the fail point is now at 55% copying files.

Lots of issues here.

1 - the install process for devices is broken on win10, has happened to too many people.  It worked on win7/8 so not sure what microsoft have changed to break it, possibly that win7 would ignore issues and proceed with install and you would then have to fix manually after install.
2 - the upgrade process to a new win10 build repeats the entire process, why? the OS is already installed, this has a lot of issues, such as the one I am having, but also if someone has spent the time manually fixing drivers, I assume those changes would be undone with the update that refreshes all devices drivers.
3 - why is the installer lying about copying files when its really setting up devices?

So given I have moved the fail point I am guessing this is some kind of device driver issue.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 02, 2015, 04:30:33 PM
Quote
3 - why is the installer lying about copying files when its really setting up devices?

I would imagine that the update process is incremental.
The process works out what to install and as the process moves forward kicks off child processes to do the install.
That is why the the 'sliding bar', sits for periods and jumps random amounts :)

It does not look as good to display 'Copying Files and doing other stuff you don't need to know ....' :D
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: NewtronStar on September 02, 2015, 10:31:15 PM
Chry i spent about 5 days trying to get the the sound card to play 5.1 sound on windows 10 all it could do was 2.0 and the driver came from manufacture explicitly for windows 10 but it must have been a beta.

No issues with GPU Nvida drivers or motherboard drivers, it does not matter anyway have gone back to windows 8.1  ;)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 02, 2015, 11:57:37 PM
I ran SFC and was a fair few corrupted files, and one file couldnt be repaired because the backup was also corrupted :D.

Since then I have been bench stressing the hardware to make sure ok and its all passing.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 03, 2015, 12:09:34 AM
I ran SFC and was a fair few corrupted files, and one file couldnt be repaired because the backup was also corrupted :D.

Since then I have been bench stressing the hardware to make sure ok and its all passing.

Interesting,

Have you got a backup where the SFC run would complete 100% good ?
It is likely that if there was System file corruptions there will be data corruptions & possibly corruptions in the registry as well.
You need to get to a known good position to start/update from.

The errors could be that the information being read during the update does not make sense.
The errors are basically some code falling through because it is finding something it should not be able to, rather than the actual error it is pointing at being real.
(Baroque sentence structure..... Sorry ;D)



Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 03, 2015, 02:12:04 AM
I am going to reinstall the OS, I will try this famous built in option to do a clean install as I am curious how clean it is.

Waiting for latest hardware tests to finish.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 03, 2015, 02:27:27 AM
... built in option to do a clean install as I am curious how clean it is.

That will be interesting to see what MS thinks a clean re-install is. :D
Let us know how it goes.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: c6em on September 04, 2015, 08:35:20 AM

Can I ask you all: honestly - why are you bothering?
You (and those on the MSE techie forum) seem to be wasting a lot of your time on this, just about everyone remotely techie should have known it was going to be total screwup.
The fact that it was offered free should have been a red light warning to anyone: effectively those who upgraded are the beta testers, with those on the technical preview program as the alpha testers.

Yes, I can see those who work in mending PC's as a job would need to know the ins and out and all the problems of Win 10.
The rest of us should be leaving it all to everyone ELSE to get all the problems over the next year and then upgrade if you want to in July 2016.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 04, 2015, 08:40:16 AM
@c6em
In a nutshell you are right.
But, there is always the 'pull' of a new OS.
The people who know MS well still want to marvel at the new toys :D no matter what they may expect.

Sent from my LG-D855 using Tapatalk

Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 03:47:42 AM
haha

well

The update is I initially did a so called clean reinstall the method microsoft claim is the way to go which is to do a reset via the settings, this left directories such as windows.old in place on the c: drive :) and the exact same files were corrupt and not repairable.

I then made a new iso with the media creator tool and did a proper clean install, this time even when I ran sfc before doing anything to the pc it had to fix 2 files, but was able to fix them (there was updates forced down to the pc whilst it was running).

I had to register it again for the inssider testing and waiting for the new build to be offered to me again.

Ram etc. tested fine on my tests and I was quite thorough.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Bowdon on September 05, 2015, 10:27:30 AM
Is this the new version thats supposedly coming out in November called Threshold 2? http://www.winbeta.org/news/windows-10-threshold-2-update-now-slated-for-november-launch (http://www.winbeta.org/news/windows-10-threshold-2-update-now-slated-for-november-launch)

Also its interesting you mentioned about generic devices. That's what happened with my HP printer. When I updated to win10 from win7 windows update kept telling me I had 2 updates for my printer. But the updates kept failing and I couldn't figure out why. I went to the HP forum and there was loads of people with the same problem.

I had a clue that something was wrong with the printer issue as I ran the HP update program and it said there was no new drivers for the printer. So I thought how come thats saying no drivers, yet windows is saying 2.

After a while I noticed a post by one guy who said, 1. re-install the original printer driver over the top of the ones installed. 2. go in to device manager and delete the generic printers in the printer section. I found I had 2, which makes sense as there is a printer and fax facilities on the printer and both are listed seperately. After I did that the 2 printer windows updates vanished and all was well.

But from reading that HP forum there was a LOT of people going through the same issues. I do wonder if there is a general device problem when upgrading windows versions. For some reason it doesn't recognise the drivers, or they get corrupted (I installed the same version of driver as what was working in win7).
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: c6em on September 05, 2015, 10:53:55 AM
Latest gem from the MSE techie site on Win10 suggests that if you upgrade a retail copy of win 7/8 to win 10 then you cannot subsequently transfer the win10 install to another computer if you PC packs up - you will have to buy a new win10 licence

So as I see it - and if true of course! you are 'paying' for the free upgrade by having your retail licence converted into a OEM licence - and hence you should only upgrade OEM licences and not retail licences.
You will still of course be able to buy a 'full new retail copy' of win 10 which will be transferable I'd imagine.
See link to the source of this new info - which does claim to be quoting a MS official answer.
http://www.expertreviews.co.uk/software/operating-systems/1403707/windows-7-and-8-retail-users-cant-transfer-windows-10-after-a (http://www.expertreviews.co.uk/software/operating-systems/1403707/windows-7-and-8-retail-users-cant-transfer-windows-10-after-a)


Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 05, 2015, 11:26:13 AM
I can believe this, but we need to wait for full confirmation.
i.e. Some MS bod is prepared to put his/her name to a official quote.

Sent from my LG-D855 using Tapatalk

Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 02:48:52 PM
yeah this was in the news before release, the retail licenses are converted to OEM.  The fact you dont get a key backs this up, when I clean reinstalled win10 I didnt put in a key it just remembered the activation for the hardware.

I made sure i didnt waste any of my win7 ultimate keys on this machine, used up a spare pro key.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 05, 2015, 03:14:10 PM
The fact you dont get a key backs this up, when I clean reinstalled win10 I didnt put in a key it just remembered the activation for the hardware.

I thought the idea was that no-one got a key and win10 creates a unique key on the basis of the hardware config. (Unique HD serials etc etc etc ....)
The idea being if MS recognise the unique ID, you are activated on install of win10.
If the unique id is not recognised you will be pointed/pushed to buy the appropriate license.

I thought it was an attempt to work around all the hacks/cracks that enable you to install windows7/8 for free.

I have not seen a retail win10 install, so this may be all fiction :D :D
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 03:21:45 PM
still fails, same place, it would seem the only way I can keep latest build is to clean install the latest build (although that might fail), the upgrade process is flawed.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 05, 2015, 04:11:23 PM
Quote
the upgrade process is flawed
Understated to perfection :)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 09:38:42 PM
on neowin I am been told I did "something wrong" :D

yeah its really hard to hit the update button :p
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 09:40:12 PM
as far as i know the retail copies do give you a key.  But I am not 100% sure.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 05, 2015, 09:40:28 PM
on neowin I am been told I did "something wrong" :D

yeah its really hard to hit the update button :p

I totally agree with Neowin ......... You let win10 touch your machine.!  ;)

 :lol: :lol:
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 10:22:11 PM
umm seem we been posting in wrong thread? can kitz or another mod be kind enough to move these to the win10 thread? http://forum.kitz.co.uk/index.php/topic,16089.msg299185.html#msg299185

thanks, and apologies to others in this thread.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: roseway on September 05, 2015, 10:52:13 PM
Moved as requested.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 05, 2015, 11:15:33 PM
thanks eric :)

By the way guys I clean installed 10532 which seems fine, so the upgrade process is bugged.

Incidentally since we mentioned keys, using the 10532 installer I was twice asked for  key and I just skipped the prompts, it is still activated.

The 10532 iso I made using a guide from the files windows update downloads so its a home made iso.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 05, 2015, 11:20:04 PM
That points to the scenario I described. Your machine is known from the previous install.
Did you blitz the drive before the clean install?
Maybe something is hidden on the disk?
Don't know.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 06, 2015, 12:18:52 AM
yeah the ssd partition table was wiped and repartitioned.  Thats the only way I clean install machines.

By the way I have a new theory why the upgrade failed.  I made a discovery of something broken in 10532.

So the first news is that automated driver updates seem to be gone in 10532, I left it sitting there for a while,nothing, then ran a manual update checkm also nothing.  So had to manually install nvidia drivers which I see as a good thing.

The issue I have discovered is that hyperV seems broken, if I try to activate it then on a reboot it gets to 99% setting it up and then rolls back with a failure. :p

So I am going to go back to 10240, keep HyperV off and then try to update again as I am curious.
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 06, 2015, 12:36:09 AM
You are a glutton for punishment.

Just wring its neck quickly and put it out of its misery. <jk>

To any concerned readers I couldn't do this for real. OK :)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: Chrysalis on September 06, 2015, 10:33:59 PM
ok the culprit is indeed HyperV, also I got a thank you from a guy who found my neowin thread on google and did confirm it fixed his as well.  All the fanboys have suddenly gone a bit silent. :)
Title: Re: Win10 build 10532 = fail yet again LOL
Post by: AArdvark on September 06, 2015, 11:05:24 PM
Well done.

Problem solved until the next big update !  ;D ;)