Hi,
I have a Packard Bell OneTwo S3221. It came factory installed with W7.
I upgraded to W10 last year after difficulty - upgrading to W10 via Windows update would not work, kept installing to a certain percentage then would reboot to a blank screen and freeze indefinitely, I needed to power off then on restart it would roll back to W7. This happened repeatedly despite trying all sorts - clean boots, uninstalling antivirus and updating drivers, etc.
I finally installed W10 using Media creation tool. Everything ran fine. But when the big update came in Novmember 2015 that failed to, in the same way as above, however all other monthly windows updates install fine.
Windows update never tried to push the Nov 2015 update on me again - I'm still on build 10240 now.
I was prompted to install the anniversary update by Windows update last week but that also failed in the same way as above. Download ok and begins installing fine, then at some point after 50% complete I get the blank screen indefinitely and have to power off, then it reverts back to W10 build 10240.
Having checked Packard Bell website my model is not supported by Packard Bell for W10, and they are not providing any drivers for it. This may explain the problems.
Can anyone suggest how to find out what the problem is and if there is a solution? I've tried looking in Update history for error codes, but there is none, it doesn't even show an attempt to install the anniversary update. Like i said every other monthly update since last year installs fine, its just the big builds that won't.
Thanks
Hi, simplest answer is avoid windows update and create the appropriate bootable medium or iso and use it as you did before. That way you can try again without the download.
As you know plenty of people have this sort of problem. Make sure you have at least 450Mb of unallocated space on the drive.
You could try reading the Windows update log...
Note that the upgrade can introduce new issues for some (search the net), and some are delaying because of that. Older machines like yours could well exhibit such problems. So before you make this change, I recommend you create a disk image of your existing setup - a procedure you should do routinely anyway- to give another way of restoring your system.
E.g. Macrium Reflect (free) + its boot medium + external storage for images.
It's best to have a physical bootable medium as it covers all of:
a. if you need to repeat the installation
b. as a bootable medium for recovery options
c. in case you need to do an in-place upgrade repair install
without taking up disk space.
I had problems installing (well trying the preview versions) on a moderni-ish Dell i5 laptop. Nothing would get me a working version of Ten, and the installs or upgrade installs (I tried all options) all failed.
What did work was totally deleting everything on the drive, in other words use the install media to take the drive down to 'unallocated' space by using the advanced install options provided. That worked like a charm and Ten installed in little more than a few minutes. That was at the end of last year. I've just clean installed the AU the same way.
Why it wouldn't install before was always a mystery.
This has happened on several computers here too unfortunately , either with 240 or 380 and I still have two that haven't been offered AU yet. Pretty sure I used the Inplace Upgrade Tutorial back then to get around it and save my files though I have since Done clean installs on the problem Comps too.
Repair Install Windows 10 with an In-place Upgrade - Windows 10 blog[2]=Installation%20and%20Setup
Thanks for the replies. I have been away so have only just got around to trying the suggestion of using the Media creation tool to force the W10 anniversary update through.
It still failed with the windows media creation tool at around 84% and reverted back to W10 build 10240 as before, but the creation tool did give me an error message:
0xC1900101 - 0x4000D
The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation
Hi this is a relatively well known message often associated with driver updates or other update issues. Searching for the text or the error message will point you in the right direction, maybe lead to a solution. Some examples:
Possible Fix for error 0xC1900101 - 0x4001E and 0x4000D : Windows10
Microsoft Community
Solved Install stuck at 75% - Windows 10 blog
