Windows 10 resoration disk?

I had a problem today when the computer faild to boot up.
I did as the b/w scrren instructed and inserted the Win10 installation
disk and booted up from this.
I got a blue screen with various options, one of which was to access
"System Restore" and fix the problem by going back to yesterday's
system.
But there was no System Restore to be had ecen though the machine
regularly creats one on each startup. It kept asking for for the
"correct operating system"! I did all the usual disconnecting all
other drives all to no avail. Why can't this method access the
system restore?
I noticed the menus all referred to Windows7 which was the OP before
the Win10 download, so ghosts of Windows7 lurk forwver in the system!
Anyway, I fixed it by booting up from the Macrium "rescue disk" and
this had a "boot rescue" section and which faithfully indicated a
Win10 OS.

Wy does Macrium rescue work and Windows' doesn't?

Evidently my HDD has junk material belonging to the old Win7 days: how
can I get rid of this? Can I download a new latest installation disk
to a new HDD and transfer all data & programs across to this, leaving
behind all the old Windoew 7 stuff? Is there software to do
this.....help.

Peter Jason wrote:
I had a problem today when the computer faild to boot up.
I did as the b/w scrren instructed and inserted the Win10 installation
disk and booted up from this.
I got a blue screen with various options, one of which was to access
"System Restore" and fix the problem by going back to yesterday's
system.
But there was no System Restore to be had ecen though the machine
regularly creats one on each startup. It kept asking for for the
"correct operating system"! I did all the usual disconnecting all
other drives all to no avail. Why can't this method access the
system restore?
I noticed the menus all referred to Windows7 which was the OP before
the Win10 download, so ghosts of Windows7 lurk forwver in the system!
Anyway, I fixed it by booting up from the Macrium "rescue disk" and
this had a "boot rescue" section and which faithfully indicated a
Win10 OS.

Wy does Macrium rescue work and Windows' doesn't?

It's amazing, isn't it. I've noticed this. And part of my
procedures now, is the run the Macrium CD "boot repair" thing
first, *before* giving Windows a chance to look at it. It's
a one-two punch, with Macrium not able to do the whole
job, but like some kind of fertilizer, it lays down
sufficient good info, such that the Windows Repair
finished the job. I think to some extent, it's the
Macrium ability to assign new GUIDs to things that
helps (like, when there are identifier conflicts for
OS partitions).

I don't really think Macrium has written custom software to
do this. Rather, Macrium is using Microsoft utilities, but using
them in a certain order. And perhaps, being a bit more
inquisitive about the system than a generic Microsoft approach.

Otherwise, I can't explain it. Because I have been in a situation
where Windows couldn't repair after three passes, but one kick
at it with Macrium, the Windows thing fixed it after that and
could boot.

You can't "repair" something that's trashed. If your C: got
corrupted somehow, then there's going to be a large class of
failures that no amount of CHKDSK will fix. But for the easy
stuff, like incorrect identifiers in the BCD file or in the
Registry that backs the BCD, there is hope.


Evidently my HDD has junk material belonging to the old Win7 days: how
can I get rid of this? Can I download a new latest installation disk
to a new HDD and transfer all data & programs across to this, leaving
behind all the old Windoew 7 stuff? Is there software to do
this.....help.

I'd agree, that some part of your upgrade sequence left
something behind.

When you upgrade from Win7 to Win10, the Win7 OS portion
moves to C:\Windows.old, the Win10 is stored in C:\Windows.
The Windows.old either gets deleted by your usage of
cleanmgr.exe, or it gets removed automatically after
30 days (original Win10) or 10 days (some later Win10).
So thirty days max, all vestiges of Windows 7 are gone.

That leaves remnants in the BCD file. Or really, any partition
sitting on one of your disks, that happens to contain Windows 7.
The various Microsoft tools can scan drives looking for OSes,
so they will be able to spot some OS you left behind.

Using the Macrium CD, booting from it, doing the boot repair
from there, while *only* the System Reserved and C: of the
desired Win10 are present, you should be able to repair the
BCD boot info for that hard drive or SSD drive. Just make
sure that interfering drives are removed.

I have certain procedures for cleaning white space, which
I don't run all that often. If you actually believe some
"invisible" partition is doing it, you could vacuum all
the disks and spruce them up. For example, you are allowed
to run "diskpart" from the Win10 Installer DVD command
prompt. You can do a "clean all" of a hard drive from
there. It might take five to eight hours. The entire
drive will be zeroed. Then, using your Macrium CD, you
can start a restore, and restore System Reserved and
C: partition. Now, you know for sure that the disk was
clean as a whistle before you started, and only
Windows 10 is going back. The disk will be so clean,
Photorec or Recuva will not find anything in those
sparkling clean sectors.

So if you craft your sequence of disk operations
right, it's possible to hoover out every bit of
"history" on the machine. One of the reasons
Macrium fits into this process so well, is
only "active" files are backed up. The clusters
containing deleted files don't get backed up.
If you establish a "zeroed disk background" before
doing a restore, then only the active files on
each partition being restored by Macrium, are now
on the disk.

Now, I don't really think all of this is necessary,
and I only mention it, if you need a hobby or
something... :-) Maybe this has something to do
with you using GPT on a very large OS hard drive,
and maybe something in the GPT partition table
contains Win7 info, but it should not be the
kind of info to confuse a BCD. Because to work
on a BCD, the registry of the prospective OS
must be examined. There actually has to be
an OS partition for that to work. You can't
populate a BCD with bogus info, unless there
is an OS partition sitting there with info
that a BCD editing tool can use.

Paul

"Peter Jason" wrote in message
...

Can I download a new latest installation disk
to a new HDD and transfer all data & programs across to this, leaving
behind all the old Windoew 7 stuff? Is there software to do
this.....help.

If your question is can you replace the existing HD(old) in the device with
a new HD(new) and then *transfer* software without *reinstalling* software
from the 'old' to the 'new' device, then the answer is no.

Data can be copied from the old HD to the new HD as long as both devices are
accessible by Windows.

One could 'restore' an image made(o/s and software and if included data if
on a different drive/partition) of the old(HD) to the new(HD)....but that
wouldn't necessarily be termed as a 'transfer'.

--
....winston
msft - mvp 2007-2016, insider mvp 2016-2018

On 11/11/2017 2:38 PM, Peter Jason wrote:
I noticed the menus all referred to Windows7 which was the OP before
the Win10 download, so ghosts of Windows7 lurk forwver in the system!
Anyway, I fixed it by booting up from the Macrium "rescue disk" and
this had a "boot rescue" section and which faithfully indicated a
Win10 OS.

Wy does Macrium rescue work and Windows' doesn't?

Evidently my HDD has junk material belonging to the old Win7 days: how
can I get rid of this? Can I download a new latest installation disk
to a new HDD and transfer all data & programs across to this, leaving
behind all the old Windoew 7 stuff? Is there software to do
this.....help.

Do you have data on that hard disk? Backup them first!

--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa