Can W7 (re)install leave partitions as they are? (And other questions.)

J. P. Gilliver (John) wrote:
In message , "J. P. Gilliver
(John)" writes:
[]
Now at 68% - 563955 of 625111 - and has been for some time. Mouse
cursor still movable, disc light flashing briefly about once a second.

_Still_ at exactly the same stage over 5 hours later. I did try the
escape key, and it came up with a message to the effect that upgrade
cannot be stopped at this point as it might leave the computer in an
unusable condition, so it hadn't frozen or anything - but it didn't seem
to be _doing_ anything, either (still the very slight flashes from the
disc light). The message only had an OK button, which I clicked and it
went back to doing the upgrade (or not).

The message _did_ take some tens of seconds to appear, which suggests
it's doing _some_thing that's taking most of its attention, but I can't
think what; it's not online, and I declined its offer to fetch updates
at the start of the process anyway. And besides, at this stage it _says_
it's only transferring files and functions, or something like that.

We've left it overnight, and will probably leave it tomorrow as we have
something else to do, but I fear we're going to have to interrupt it
after that, at least if it hasn't shown any change in the numbers. (And
possibly even if it has, if extrapolating to completion is _too_ long.)

If you could get Task Manager running, maybe you can
take a look for "the usual suspects". I doubt at the 60% mark though,
there is a desktop running.

Paul

In message , "J. P. Gilliver
(John)" writes:
In message , "J. P. Gilliver
(John)" writes:
[]
Now at 68% - 563955 of 625111 - and has been for some time. Mouse
cursor still movable, disc light flashing briefly about once a second.

_Still_ at exactly the same stage over 5 hours later. I did try the
[]
Another 8 hours - and now 71% (609695 of 625111)!
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

I long for the commercialised Christmas of the 1970s. It's got so religious
now, it's lost its true meaning. - Mike [{at}ostic.demon.co.uk], 2003-12-24

In message , Paul
writes:
[]
If you could get Task Manager running, maybe you can
take a look for "the usual suspects". I doubt at the 60% mark though,
there is a desktop running.

Paul
Indeed. I haven't tried a ctrl-alt-delete, but Alt-Tab didn't bring up a
bar at all. As you will see from my other post, it has moved another
whole 3% overnight, so might finish in 80 hours; we're otherwise
occupied this morning, so will see what happens; if it was me I'd be
inclined to leave it to completion (or complete stall), but the ultimate
decision is Julia's (-:!
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Fortunately radio is a forgiving medium. It hides a multitude of chins ...
Vanessa feltz, RT 2014-3/28-4/4

J. P. Gilliver (John) wrote:
In message , Paul
writes:
[]
If you could get Task Manager running, maybe you can
take a look for "the usual suspects". I doubt at the 60% mark though,
there is a desktop running.

Paul
Indeed. I haven't tried a ctrl-alt-delete, but Alt-Tab didn't bring up a
bar at all. As you will see from my other post, it has moved another
whole 3% overnight, so might finish in 80 hours; we're otherwise
occupied this morning, so will see what happens; if it was me I'd be
inclined to leave it to completion (or complete stall), but the ultimate
decision is Julia's (-:!

Yes, but don't forget that the "percentage system" is non-linear.
Portions of the procedure are assumed to represent some percentage
of the whole. When it hits 66%, you might see it begin to fly.
I would not extrapolate what is happening right now, because
when it gets to the next way-point, the "scale" of that
indicator is going to change.

What I like about this particular one, is when an install fouls
up, the "percentage" value can be used in a Google search, and
typically there are known failure modes versus percentage. And
that means the percentages are "the beginning of the next phase"
and so on. So the developers (and the users) know that the
62% one is caused by a particular thing. The percentage indication
is not a simple relationship versus clock-time.

Paul

In message , Paul
writes:
J. P. Gilliver (John) wrote:
[]
me I'd be inclined to leave it to completion (or complete stall), but
the ultimate decision is Julia's (-:!

Yes, but don't forget that the "percentage system" is non-linear.
Portions of the procedure are assumed to represent some percentage
of the whole. When it hits 66%, you might see it begin to fly.

Yes-stayed at 66% for ages, and 68% for ages; next time I looked 71%,
then 72 (617827 files); now it's still 72% but 624942. We'll see what it
is after we've been out shopping (-:

I would not extrapolate what is happening right now, because
when it gets to the next way-point, the "scale" of that
indicator is going to change.

What I like about this particular one, is when an install fouls
up, the "percentage" value can be used in a Google search, and
typically there are known failure modes versus percentage. And
that means the percentages are "the beginning of the next phase"
and so on. So the developers (and the users) know that the
62% one is caused by a particular thing. The percentage indication

True, although the discussions in the links that have appeared in this
thread don't _seem_ to have been related (and I think all of them were
doing an upgrade from Vista to 7SP1, whereas I'm trying to do a repair
from 7SP1 [upgraded from 7SP0] to 7SP1.

is not a simple relationship versus clock-time.

Paul

Fingers crossed (-:!
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

10.0 times 0.1 is hardly ever 1.0.

In message , "J. P. Gilliver
(John)" writes:
[]
Yes-stayed at 66% for ages, and 68% for ages; next time I looked 71%,
then 72 (617827 files); now it's still 72% but 624942. We'll see what
it is after we've been out shopping (-:

No change after all day )-:.
[]
What I like about this particular one, is when an install fouls
up, the "percentage" value can be used in a Google search, and
typically there are known failure modes versus percentage. And
that means the percentages are "the beginning of the next phase"
and so on. So the developers (and the users) know that the
62% one is caused by a particular thing. The percentage indication
[]
Googling for

Windows 7 repair 72%

certainly shows it's far from unusual, but the solutions offered seem
many and varied, and _mostly_ related to upgrading from Vista, rather
than the repair I'm doing. One that's come up is the possibility of
adding an environment variable

Variable Name: MIG_UPGRADE_IGNORE_PLUGINS
Variable value: IphlpsvcMigPlugin.dll

, but (a) that means I have to get back to a working system to do it,
and (b) sounds to me more something that'd cure problems in the first
stages rather than "72%" through the last stage.

If it hasn't move when I go back downstairs after this reading session,
though, I think we'll have to interrupt it and see what happens.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The fifth bestselling detail of all time: the Ford Transit. (RT/C4 2015-5-24.)

J. P. Gilliver (John) wrote:
In message , "J. P. Gilliver
(John)" writes:
[]
Yes-stayed at 66% for ages, and 68% for ages; next time I looked 71%,
then 72 (617827 files); now it's still 72% but 624942. We'll see what
it is after we've been out shopping (-:

No change after all day )-:.
[]
What I like about this particular one, is when an install fouls
up, the "percentage" value can be used in a Google search, and
typically there are known failure modes versus percentage. And
that means the percentages are "the beginning of the next phase"
and so on. So the developers (and the users) know that the
62% one is caused by a particular thing. The percentage indication
[]
Googling for

Windows 7 repair 72%

certainly shows it's far from unusual, but the solutions offered seem
many and varied, and _mostly_ related to upgrading from Vista, rather
than the repair I'm doing. One that's come up is the possibility of
adding an environment variable

Variable Name: MIG_UPGRADE_IGNORE_PLUGINS
Variable value: IphlpsvcMigPlugin.dll

, but (a) that means I have to get back to a working system to do it,
and (b) sounds to me more something that'd cure problems in the first
stages rather than "72%" through the last stage.

If it hasn't move when I go back downstairs after this reading session,
though, I think we'll have to interrupt it and see what happens.

If you did a backup first, it can sometimes be faster
to restore from backup, then to wait a few hours for
the install attempt to "unwind". It will probably unwind
successfully if you terminate it. Probably.

Did you make a backup ?

Paul

In message , Paul
writes:
J. P. Gilliver (John) wrote:
[]
71%, then 72 (617827 files); now it's still 72% but 624942. We'll
[]
If it hasn't move when I go back downstairs after this reading
session, though, I think we'll have to interrupt it and see what
happens.

If you did a backup first, it can sometimes be faster
to restore from backup, then to wait a few hours for
the install attempt to "unwind". It will probably unwind
successfully if you terminate it. Probably.

Did you make a backup ?

Paul

Had made image. On forcing powerdown and restart, it said upgrade
unsuccessful, restoring, which it then did - taking 10-20 minutes at the
outside; To restore from the image (via USB tool, +100G) would have
taken longer, I think, though we didn't know that as it gives no
progress bar, only a fake one that I guess is just to show it hasn't
locked up.

I _think_ sulk mode has gone, for a hardware-related reason rather than
Windows corruption; I'll get Julia to use it as much as possible over
the next few days, and tell you what it was if all _is_ now well!
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

When I'm good, I'm very good. But when I'm bad - I'm better! (Mae West)