View Single Post
  #16   Report Post  
Posted to uk.d-i-y
Martin Brown[_2_] Martin Brown[_2_] is offline
external usenet poster
 
Posts: 1,449
Default On one PC, Windows 7 to Windows 10 update fails at 'fetching

On 07/02/2020 23:23, wrote:
On Thursday, 6 February 2020 20:07:24 UTC,
wrote:
I have been trying to update a neighbour's PC from Windows 7 to
Windows 10, using
https://www.microsoft.com/en-gb/soft...load/windows10 .

I have tried the "direct" method in her abode, using her Virgin
Media Internet service.

I have tried the "direct" method in my abode, using my pseudo-BT
Internet service.

I have used my Win10 PC to create a USB transfer drive in order to
use it to update her PC in my abode (using pseudo-BT Internet).


In each case, the process update sticks at "fetching updates: 46%"
- I have on occasion waited for over an hour.



I don't have any other Windows 7 PCs to try.

Her PC is nominally over 12 years old, but in Summer 2015 all the
electrics and electronics, including the mains lead, were changed
to middle-spec then-modern, and Windows 7 pro was installed. Only
the case was retained.

When her PC was moved to here, it was connected to my spare
keyboard, mouse, screen, and hers were left in situ.



Any suggestions as to what to do next?



THIS IS A GENERAL REPLY TO WHAT HAS BEEN POSTED UP TO NOW

Since the update fails at the same point whether or not I use the USB
method, I'm continuing just with the direct update using only the
neighbour's machine.


BG So are you saying that the media creation tool simply stops
downloading?

I'm saying that it gets to "fetching updates: 46%" and there is no
further apparent progress. I add that there is then irregular
intermittent disc activity, to judge by the light.

DIR says that C: has almost 399 GB free; File Explorer says "371 GB
free of 465 GB". Surely that should be enough?

pog Any antivirus?

AVG free, and Malwarebytes. Both show no faults, though AVG
indicates that there is work for the paid version of AVG.

BG ...


Pressing F2 or Del during boot gets something which calls itself
"ASUS UEFI BIOS utility -EZ Mode"

BG copying a message from Chris Hogg which I do not see ...


After non-completion of the conversion to Windows 10, it always boots
to Windows 7 just as before.

AB Is the O/P booting from the USB stick, or running the setup.exe
on the stick from within the existing win7?


I tried the stick once, using the existing Win7 to run the stick's
setup.exe.

Otherwise I use the update-in-place method, without USB.

GM Install Linux Mint? [g]

That would baffle her completely.


NEW RESULTS, NO BETTER.

A remote ally has just E-mailed to say that he has just successfully
done a free Windows 7 to Windows 10 update-in-place by this method.

pog Try deleting everything from
C:\Windows\SoftwareDistribution\Download
(Don't need to remove the folder
C:\Windows\SoftwareDistribution\Download\SharedFil eCache)


No SharedFileCache. I moved the rest to \STUFF\ on my IMPACT USB and
removed the USB. Shut down. Did a cold reboot, logged in as
LocalAdmin, tried the "direct" method, without any USB present.
Still sticking as 46%; disc activity light shows weakly active.
22:30 to 23:05. Shut down.


I'M NOW OUT OF IDEAS, apart from getting it done commercially - it
seems that the PC itself is at fault.


Patience grasshopper, patience. It seems that one some legacy machines
the damn thing can sit at 46% for a few hours before moving on. I have
no idea what it is doing but MSKB threw up this exact response.

https://answers.microsoft.com/en-us/...5-deaa623cbd7e

I hope it helps. The other one I have seen but with Win7 updates is a
failed update somewhere in the past history (last few years) leaving the
registry in a state that the newest upgrade cannot sort out.

This requires going into the registry with your trusty flint axe or
risking one of the automated registry checkers. My last portable was
bought secondhand at a reduced price because its upgrade had borked it.

I'd be inclined to let it sit at 46% overnight and see if that works.

--
Regards,
Martin Brown