• Getting a new computer

    From Jim the Geordie@21:1/5 to All on Tue Feb 4 20:41:19 2025
    I have had my pc since 2010.
    It is Windows 10 with all the updates, but is feeling a bit tired and
    anyhow I fancy a new one.
    It is running fine, but too limited for Windows 11 and I will have to
    bite that bullet sooner or later.
    I think I installed everything that is there to a virgin m/c at the time
    and although I have the time and know-how to do it all again, I wondered whether my local computer dealer could copy over everything to a new pc
    OR should I just take it to him and have the necessary upgrade to this
    m/c and leave the hard drive as it is (it has plenty space).
    I suppose it might be possible just to transplant the hard drive to a
    new machine - I just don't know, which is why I'm asking.
    I also have an external HDD running Macrium backup.
    If I were to do it myself, I'm not sure I have the original discs/downloads/passwords for all the programs.
    TIA
    Please don't suggest Linux as I'm really too old to begin that learning
    curve.
    --
    Jim the Geordie

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Jason@21:1/5 to jim@jimXscott.co.uk on Wed Feb 5 09:07:14 2025
    On Tue, 4 Feb 2025 20:41:19 +0000, Jim the Geordie
    <jim@jimXscott.co.uk> wrote:

    I have had my pc since 2010.
    It is Windows 10 with all the updates, but is feeling a bit tired and
    anyhow I fancy a new one.
    It is running fine, but too limited for Windows 11 and I will have to
    bite that bullet sooner or later.
    I think I installed everything that is there to a virgin m/c at the time
    and although I have the time and know-how to do it all again, I wondered >whether my local computer dealer could copy over everything to a new pc
    OR should I just take it to him and have the necessary upgrade to this
    m/c and leave the hard drive as it is (it has plenty space).
    I suppose it might be possible just to transplant the hard drive to a
    new machine - I just don't know, which is why I'm asking.
    I also have an external HDD running Macrium backup.
    If I were to do it myself, I'm not sure I have the original >discs/downloads/passwords for all the programs.
    TIA
    Please don't suggest Linux as I'm really too old to begin that learning >curve.

    I would hire a pro to handle it.
    Go to a shop and choose a machine with a max CPU and Ram, get
    everything installed by them. Give them all the money they want.

    If you decide to do it yourself, punch the tar baby first, just for
    practice.

    Avoid the "Msoft account" imbroglio. and the "cloud".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Graham J@21:1/5 to Jim the Geordie on Tue Feb 4 22:17:47 2025
    Jim the Geordie wrote:
    I have had my pc since 2010.
    It is Windows 10 with all the updates, but is feeling a bit tired and
    anyhow I fancy a new one.
    It is running fine, but too limited for Windows 11 and I will have to
    bite that bullet sooner or later.
    I think I installed everything that is there to a virgin m/c at the time
    and although I have the time and know-how to do it all again, I wondered whether my local computer dealer could copy over everything to a new pc
    OR should I just take it to him and have the necessary upgrade to this
    m/c and leave the hard drive as it is (it has plenty space).
    I suppose it might be possible just to transplant the hard drive to a
    new machine - I just don't know, which is why I'm asking.
    I also have an external HDD running Macrium backup.
    If I were to do it myself, I'm not sure I have the original discs/downloads/passwords for all the programs.
    TIA
    Please don't suggest Linux as I'm really too old to begin that learning curve.


    I suggest:

    1. Get a completely new machine, and keep the old one for reference and
    so you can ask questions here when things go wrong. That way your new
    machine will be free from any crud that has accumulated on the old one.
    Don't ask anybody else to do it for you - no local computer dealer will
    have the time or incentive to do a good job. Be prepared to allow
    several weeks of your own time. Keep decent notes of everything you do.

    2. Decide whether or not you want to use M$ OneDrive to store all your documents so they are equally available from both computers. Research
    how to do this.

    3. Set the new machine up with a Local Administrator account - review
    this newsgroup for past suggestions as to how this is achieved; it might
    not be straightforward. Add at least one Standard User account for
    everyday work - more if necessary.

    4. Set up your LAN so the old and new machines can communicate properly.
    You may have to create a Local Administrator account (and user
    accounts) to achieve this properly - read this newsgroup for a posting
    by Java Jive.

    5. If you have a stand-alone version of MS Office on the existing
    machine then you can't move it to the new one. If you use the Office
    365 subscription then you can have several (I think 5) installations on different machines. If you install any flavour of Office do so before
    you set up a login for a MSA, otherwise the Outlook PST file will be
    placed in OneDrive, which is not sensible.

    6. Be prepared to install all your required programs again. If you
    don't have the original discs/downloads/passwords then contact the
    suppliers and make sure you archive this material properly for the
    future. Installation of a program on Windows is not generally achieved
    by simply placing the .exe file somewhere sensible; most programs are
    installed via their own installation program and process. You may find
    some programs have to be different versions for W11.

    --
    Graham J

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Jim the Geordie on Tue Feb 4 19:08:12 2025
    On Tue, 2/4/2025 3:41 PM, Jim the Geordie wrote:
    I have had my pc since 2010.
    It is Windows 10 with all the updates, but is feeling a bit tired and anyhow I fancy a new one.
    It is running fine, but too limited for Windows 11 and I will have to bite that bullet sooner or later.
    I think I installed everything that is there to a virgin m/c at the time and although I have the time and know-how to do it all again, I wondered whether my local computer dealer could copy over everything to a new pc
    OR should I just take it to him and have the necessary upgrade to this m/c and leave the hard drive as it is (it has plenty space).
    I suppose it might be possible just to transplant the hard drive to a new machine - I just don't know, which is why I'm asking.
    I also have an external HDD running Macrium backup.
    If I were to do it myself, I'm not sure I have the original discs/downloads/passwords for all the programs.
    TIA
    Please don't suggest Linux as I'm really too old to begin that learning curve.

    There are three commercial utilities available, for moving programs and files from one windows OS to another. The cost of one usage of the program, is around 50.
    If you go to a computer shop, they will use the 50 program and charge you 200. A tidy profit of 150. The numbers tossed around here, the price seems to have gone up.
    Of the three programs, one of them is worse than the others (more reports of problems
    getting it to do anything right). The high price of usage, comes with a claim of
    Tech Support - a human on their end can remote in and move a program that their automation
    does not handle.

    https://www.tenforums.com/software-apps/47945-word-warning-about-laplink-pcmover-pro-3.html

    The new PCs are UEFI only and don't have CSM (compatibility mode for legacy BIOS booting).
    The original disk may be encrypted, but you can check that with

    manage-bde -status # admin terminal

    If you are sly enough, your Win10 disk may not stand a chance of booting when moved to the new machine. The disk should be cloned onto a new storage device and the new storage device inserted in the new PC. Never move your only copy
    of a boot disk into a new machine, as it's Microsoft and just about anything could happen to that disk. I learned this a long ago, while moving Win2K around.

    I have successfully (with caveats) moved a disk from one machine to another,
    on more than one occasion, and usually, by accident (stuck wrong drive into
    a machine, it booted anyway). It enumerates the new hardware, so it would
    be adding a bunch of new detections into the ENUM key. The OS isn't even that neat and tidy, and the ENUM key is not the only place that gets detections,
    so hardware detection is more of a mess than it used to be. I don't know
    if there is an easy cleaning procedure to remove hardware detections that
    are no longer valid. (As an example of stupid, I can have an NVidia vid card
    in my daily driver, and still be receiving driver updates for AMD graphics which are switched off in the BIOS. The machines tend to not forget the hardware they have seen, or at least, the drivers that did not get
    removed at some point.)

    Summary: You should have a Plan A, a Plan B, and a Plan C :-)

    Some license keying uses "tricky methods" of marking a disk. This means
    with those certain programs, you should count on most all attempts to
    move the program, to result in a loss or mis-placement of a license.
    It is not the intention of program-mover software, to hack or crack
    stuff for you. Or the management at the company, could end up in court.

    And I would think very carefully, about what you're buying (hardware wise).
    It is all too easy to buy a piece of junk, out there. The OEM computer companies can have stock of cards for their machines, which you can't
    get at retail. But expect the prices to be on the rich side, if
    such unobtanium hardware attracts you.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to Paul on Tue Feb 4 19:08:17 2025
    On Tue, 4 Feb 2025 19:08:12 -0500, Paul <nospam@needed.invalid> wrote:

    There are three commercial utilities available, for moving programs and files >from one windows OS to another.

    Is Macrium Reflect one of the three utilities?

    Here's an interesting thread that talks about using non-paid versions of Macrium Reflect to restore to different hardware, which would be one way
    to get the new laptop up and running relatively quickly, edge cases
    aside.

    Paid versions of Macrium Reflect have the ReDeploy module, of course, so
    no workarounds might be required in that case.

    <https://www.tenforums.com/backup-restore/158449-macrium-free-restore-totally-different-hardware-working.html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Char Jackson on Tue Feb 4 22:19:02 2025
    On Tue, 2/4/2025 8:08 PM, Char Jackson wrote:
    On Tue, 4 Feb 2025 19:08:12 -0500, Paul <nospam@needed.invalid> wrote:

    There are three commercial utilities available, for moving programs and files
    from one windows OS to another.

    Is Macrium Reflect one of the three utilities?

    Here's an interesting thread that talks about using non-paid versions of Macrium Reflect to restore to different hardware, which would be one way
    to get the new laptop up and running relatively quickly, edge cases
    aside.

    Paid versions of Macrium Reflect have the ReDeploy module, of course, so
    no workarounds might be required in that case.

    <https://www.tenforums.com/backup-restore/158449-macrium-free-restore-totally-different-hardware-working.html>

    An example of a dead end, is Win10 32-bit.

    And an OS where you're using CSM and MSDOS partitioning,
    I don't think loading in a few hardware drivers will make the
    difference there. You need to "transform" your disk to something
    closer to the new generation of hardware. And Repair Installs
    don't do that. Repair Installs maintain the status quo regarding boot.

    I tried to fix that with SysLinux (use SysLinux as a boot loader,
    to transform a Windows from an old boot standard to a new boot standard),
    but each web page over there, was a bottomless pit of questions,
    and I was never going to figure out how to do that from their notes.
    Syslinux is what the Rufus guy uses for his transform.

    If Macrium Reflect could re-build the Windows folder in the ESP,
    then I might believe it could have some useful functions for things
    like this. But they tend to color within the lines, and their
    capabilities never extend outside of what you can do with a WADK
    your own self (with DISM and friends).

    I could find one comment in my travels, that you could use DISM
    for this (repackage OS), but any time I've tried to package up an OS with applications in it, when the OS is sealed, all the damn applications
    disappear. For example, you would think the "emergency USB stick"
    that the Windows OS can make, you as a user would be expecting
    your applications to be carefully reproduced when the stick is used.
    But all the applications are throw away, and what good is an
    OS image with a few patches in it worth -- would you wait an hour
    for Windows to make a USB stick with so few advantages to you ?
    It's faster to just jam in the damn DVD and do a Clean Install,
    than waste time on the "we make a USB stick out of your C: " disaster.
    Because the process is not user centric, and solves no problems
    a user cares about (my files, my applications).

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to Paul on Wed Feb 5 01:10:03 2025
    On Tue, 4 Feb 2025 22:19:02 -0500, Paul <nospam@needed.invalid> wrote:

    On Tue, 2/4/2025 8:08 PM, Char Jackson wrote:
    On Tue, 4 Feb 2025 19:08:12 -0500, Paul <nospam@needed.invalid> wrote:

    There are three commercial utilities available, for moving programs and files
    from one windows OS to another.

    Is Macrium Reflect one of the three utilities?

    Here's an interesting thread that talks about using non-paid versions of
    Macrium Reflect to restore to different hardware, which would be one way
    to get the new laptop up and running relatively quickly, edge cases
    aside.

    Paid versions of Macrium Reflect have the ReDeploy module, of course, so
    no workarounds might be required in that case.

    <https://www.tenforums.com/backup-restore/158449-macrium-free-restore-totally-different-hardware-working.html>

    <snip>
    If Macrium Reflect could re-build the Windows folder in the ESP,
    then I might believe it could have some useful functions for things
    like this. But they tend to color within the lines, and their
    capabilities never extend outside of what you can do with a WADK
    your own self (with DISM and friends).

    I haven't had an opportunity to use either of the Macrium methods, but I
    would fully expect their ReDeploy utility to work properly in most circumstances. The other approach, using non-paid versions of Reflect,
    that one could be a little less likely, maybe only 75%.

    I guess Macrium wasn't one of your top three.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Char Jackson on Wed Feb 5 03:42:57 2025
    On Wed, 2/5/2025 2:10 AM, Char Jackson wrote:
    On Tue, 4 Feb 2025 22:19:02 -0500, Paul <nospam@needed.invalid> wrote:

    On Tue, 2/4/2025 8:08 PM, Char Jackson wrote:
    On Tue, 4 Feb 2025 19:08:12 -0500, Paul <nospam@needed.invalid> wrote:

    There are three commercial utilities available, for moving programs and files
    from one windows OS to another.

    Is Macrium Reflect one of the three utilities?

    Here's an interesting thread that talks about using non-paid versions of >>> Macrium Reflect to restore to different hardware, which would be one way >>> to get the new laptop up and running relatively quickly, edge cases
    aside.

    Paid versions of Macrium Reflect have the ReDeploy module, of course, so >>> no workarounds might be required in that case.

    <https://www.tenforums.com/backup-restore/158449-macrium-free-restore-totally-different-hardware-working.html>

    <snip>
    If Macrium Reflect could re-build the Windows folder in the ESP,
    then I might believe it could have some useful functions for things
    like this. But they tend to color within the lines, and their
    capabilities never extend outside of what you can do with a WADK
    your own self (with DISM and friends).

    I haven't had an opportunity to use either of the Macrium methods, but I would fully expect their ReDeploy utility to work properly in most circumstances. The other approach, using non-paid versions of Reflect,
    that one could be a little less likely, maybe only 75%.

    I guess Macrium wasn't one of your top three.


    The utilities in question, are a product made by LapLink,
    that moves your programs over.

    https://go.laplink.com/product/pcmover-professional

    There is a Zinstall product that does the same thing.

    https://www.zinstall.com/products/zinstall-migration-move-to-new-computer-to-windows-7-with-all-your-programs-and-files-no-reinstalls

    The Easeus one, it's third in the list. When I tested the "free" version,
    it could not correctly list the contents of my Program Files area.
    That counts as a bad start, in my book.

    https://www.easeus.com/free-pc-transfer-software

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jerryab@21:1/5 to jim@jimXscott.co.uk on Wed Feb 5 09:59:48 2025
    On Tue, 4 Feb 2025 20:41:19 +0000, Jim the Geordie
    <jim@jimXscott.co.uk> wrote:

    It is Windows 10 with all the updates

    Decide on the configuration you want, but you will be buying an older
    CPU (if Intel, then 14th is getting a bit old, IMO). AMD if you like.

    Decent UPS to keep the system up with power spikes, outages, etc.

    1TB or 2TB SSD (1TB is good, 2TB if you want more space)
    32GB memory
    Decent video (whatever works for you and your programs)
    Internal HDD if you want/need one).
    External HDD (4TB to 8TB are inexpensive--make regular backups of C
    DATA)
    Replace all external cables with new. Old ones can fail unexpectedly. USB4/Lightning hub (same thing--10GB minimum,

    Check printer and other devices to see if they will work with Win11
    and will be supported. I had a Canon B&W laser printer that ran on
    Win10 but was not able to run in Win11. Canon web site stated it was
    not supported, but I bought the system with Win10--long before Win11
    was released. Had to buy a new printer (I was NOT happy with Canon's
    choice). No idea when Win12 will be offered, but within 3 yrs?

    New system w/Win11 should all be ok for Win12.

    I have used a Dell XPS and it worked fine for 8 yrs. Replaced 3 yrs
    ago with Win10 system (non-Dell)--which failed after 2 yrs. Stripped
    the hardware out and put in Intel Gen13 CPU with general specs as
    described above. Works fine. I worked in a computer shop years ago, so
    the stuff doesn't hold a lot of surprises.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Paul on Wed Feb 5 15:17:21 2025
    On 2025-02-05 00:08, Paul wrote:

    I have successfully (with caveats) moved a disk from one machine to another, on more than one occasion, and usually, by accident (stuck wrong drive into
    a machine, it booted anyway). It enumerates the new hardware, so it would
    be adding a bunch of new detections into the ENUM key. The OS isn't even that neat and tidy, and the ENUM key is not the only place that gets detections, so hardware detection is more of a mess than it used to be. I don't know
    if there is an easy cleaning procedure to remove hardware detections that
    are no longer valid. (As an example of stupid, I can have an NVidia vid card in my daily driver, and still be receiving driver updates for AMD graphics which are switched off in the BIOS. The machines tend to not forget the hardware they have seen, or at least, the drivers that did not get
    removed at some point.)

    Nearly all my PCs here are quite happily running OSs installed from
    images copied by Ghost or tars from other machines. In particular, all
    the 7+ builds originated from a single Windows 7 Ultimate build I
    created with all the software I wanted on it, which was copied
    throughout my PCs, where necessary down/upgrading it to suit the licence sticker on any given PC, and all the Ubuntu builds were copied via tars
    from a single PC.

    The machines I had/have and the OS down/upgrade paths followed are:
    2 x self-built towers (junked after my monitor burned out)
    W2k (original build on one copied to other by Ghost/SysPrep);
    Dell Latitude D610 (still works but rarely used now)
    WinXP (upgrade from above W2k; has some old music software and
    can run an old scanner which is still needed)
    Dell Precision M4300 (died)
    Win7U (the original build)
    WinXP (copied from the Latitude above by Ghost/SysPrep)
    Dell Precision M6300
    Win7U (original build copied from the M4300 when it died)
    Win7U (as above) -> Win10Pro (in place upgrade)
    WinXP (copied from Latitude above by Ghost/SysPrep)
    Ubuntu 22
    Dell Inspiron 15RSE 7520
    Win7U -> Win7HP (downgrade via a method that I devised)
    Ubuntu 22
    Dell Precision M6700
    Win7U -> Win7Pro (downgrade as above)
    Win7Pro (as above) -> Win10Pro (in place upgrade)
    Win7Pro,32-Bit (new build to run that old scanner)
    Ubuntu 22
    Dell Precision M6800
    Win7Pro (from M6700)
    Win7Pro -> Win8.1Pro -> Win10Pro (in place upgrades)
    Win7,32-Bit (from M6700)
    Ubuntu 22

    Despite the convoluted paths above, everything seems to work pretty
    well, the most significant problems have been authentication, and ...

    As you suggest, getting rid of old hardware from a Windows build is
    something of a pain. First, the slow but fairly sure and very tedious
    method ...

    Beforehand, you need to take a backup image of the OS, in case you FU.
    My personal choice is Ghost, but others are happy with Macrium, etc;
    anything reliable will do.

    You need to have an environment setting that affects the way Device
    Manager views 'absent' hardware - IMPORTANT: Note that 'absent'
    hardware includes not just hardware from any previous machines the build
    might have been on, which needs to be uninstalled, but also peripherals
    such as scanners or cameras that happen not to be attached to the PC at
    the moment, which perhaps should be left alone, depending on the
    difficulty of reinstalling them. The setting is:
    devmgr_show_nonpresent_devices=1

    To make this setting, it's not enough just to launch a command console
    and set it there, you have to do it in the environment settings
    themselves, so that the new setting will available to all running
    software, including Device Manager. These instructions are correct for
    Win 7, but should also be close or identical for later versions. It's certainly best, perhaps even necessary, to be signed on as the
    Administrator:
    <Rt-Click> My Computer/Computer
    Properties
    Advanced System Settings
    Advanced
    Environment Variables
    Choosing either ...
    Current User (preferably the Administrator)
    System
    ... click New and enter ...
    Variable name: devmgr_show_nonpresent_devices
    Variable value: 1
    Click 'Ok' all the way out.

    As it's such a long time since I set this, I can't remember whether a
    reboot is required for it to be picked up, but logically I don't think
    it should be.

    Having done this, you can go into Device Manager and choose ...
    View, Devices by connection
    View, Show hidden devices
    ... and the first time you do this may be quite a shock if your OS has
    moved around a few times!

    The non-present devices are now more obvious by not being located in the
    main ACPI* device tree where mostly they would be, but note that
    software 'devices' and other pseudo 'devices' relating to services
    aren't going to be in the tree either, so absolutely do NOT, repeat NOT,
    just delete everything not in the ACPI* tree! Also note that some of
    the off-tree devices have a faded icon, but again this alone is not
    enough of an identifier.

    What you are looking for are devices with a faded icon that have
    counterparts of present devices within the ACPI* tree, which shows that
    that is where they really belong. Those are the devices which were or
    are real, but currently are not present. Switching between 'Devices by
    type' and 'Devices by connection' may be useful here. If a device
    appears in the former with a faded icon alongside devices with a normal
    icon, and appears in the latter off the ACPI* tree, then most probably
    it's just the sort of thing you are looking for. It's up to you whether
    you choose to delete anything like USB devices that happen not to be
    attached to the PC at the moment - I tend to leave things like
    scanners, phones, cameras, alone, but delete USB drives, as otherwise
    they clutter the view so much, but that's a personal choice. What you
    should most probably do is uninstall non-present system devices such a Processors, Real-Time Clocks, Hard-disk controllers, etc, as they will
    have come from previous hardware the OS was on.

    There *used* to be a much faster way to remove old hardware from an
    image, using, IMS, an MS supplied program called DevCon.exe. By giving
    it different command lines and logging and comparing the output of each,
    you could subtract the present devices from the total devices and so
    have a list of those non-present, and then uninstall any appropriate
    items from that, but this was in the days of W2k and possible XP. I'm
    not aware of anything more modern which is as useful as that, but
    perhaps others may be able to make suggestions.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MummyChunk@21:1/5 to All on Thu Feb 6 03:59:31 2025
    Char Jackson wrote:
    On Tue, 4 Feb 2025 19:08:12 -0500, Paul <nospam> wrote:

    There are three commercial utilities available, for moving programs and files
    from one windows OS to another.

    Is Macrium Reflect one of the three utilities?

    Here's an interesting thread that talks about using non-paid versions of Macrium Reflect to restore to different hardware, which would be one way
    to get the new laptop up and running relatively quickly, edge cases
    aside.

    Paid versions of Macrium Reflect have the ReDeploy module, of course, so
    no workarounds might be required in that case.


    https://www.tenforums.com/backup-restore/158449-macrium-free-restore-totally-d ifferent-hardware-working.html



    Their trial version words fine for most tasks


    This is a response to the post seen at: http://www.jlaforums.com/viewtopic.php?p=683193632#683193632

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Java Jive on Thu Feb 13 23:17:57 2025
    On 2025-02-05 15:17, Java Jive wrote:
    On 2025-02-05 00:08, Paul wrote:

    I have successfully (with caveats) moved a disk from one machine to
    another,
    on more than one occasion, and usually, by accident (stuck wrong drive
    into
    a machine, it booted anyway). It enumerates the new hardware, so it would
    be adding a bunch of new detections into the ENUM key. The OS isn't
    even that
    neat and tidy, and the ENUM key is not the only place that gets
    detections,
    so hardware detection is more of a mess than it used to be. I don't know
    if there is an easy cleaning procedure to remove hardware detections that
    are no longer valid. (As an example of stupid, I can have an NVidia
    vid card
    in my daily driver, and still be receiving driver updates for AMD
    graphics
    which are switched off in the BIOS. The machines tend to not forget the
    hardware they have seen, or at least, the drivers that did not get
    removed at some point.)

    Nearly all my PCs here are quite happily running OSs installed from
    images copied by Ghost or tars from other machines.  In particular, all
    the 7+ builds originated from a single Windows 7 Ultimate build I
    created with all the software I wanted on it, which was copied
    throughout my PCs, where necessary down/upgrading it to suit the licence sticker on any given PC, and all the Ubuntu builds were copied via tars
    from a single PC.

    The machines I had/have and the OS down/upgrade paths followed are:
        2 x self-built towers (junked after my monitor burned out)
         W2k (original build on one copied to other by Ghost/SysPrep);
        Dell Latitude D610 (still works but rarely used now)
            WinXP (upgrade from above W2k; has some old music software and
                  can run an old scanner which is still needed)
        Dell Precision M4300 (died)
            Win7U (the original build)
            WinXP (copied from the Latitude above by Ghost/SysPrep)
        Dell Precision M6300
            Win7U (original build copied from the M4300 when it died)
            Win7U (as above) -> Win10Pro (in place upgrade)
            WinXP (copied from Latitude above by Ghost/SysPrep)
            Ubuntu 22
        Dell Inspiron 15RSE 7520
            Win7U -> Win7HP (downgrade via a method that I devised)
            Ubuntu 22
        Dell Precision M6700
            Win7U -> Win7Pro (downgrade as above)
            Win7Pro (as above) -> Win10Pro (in place upgrade)
            Win7Pro,32-Bit (new build to run that old scanner)
            Ubuntu 22
        Dell Precision M6800
            Win7Pro (from M6700)
            Win7Pro -> Win8.1Pro -> Win10Pro (in place upgrades)
            Win7,32-Bit (from M6700)
            Ubuntu 22

    Despite the convoluted paths above, everything seems to work pretty
    well, the most significant problems have been authentication, and ...

    As you suggest, getting rid of old hardware from a Windows build is
    something of a pain.  First, the slow but fairly sure and very tedious method ...

    Beforehand, you need to take a backup image of the OS, in case you FU.
    My personal choice is Ghost, but others are happy with Macrium, etc;
    anything reliable will do.

    You need to have an environment setting that affects the way Device
    Manager views 'absent' hardware  -  IMPORTANT: Note that 'absent'
    hardware includes not just hardware from any previous machines the build might have been on, which needs to be uninstalled, but also peripherals
    such as scanners or cameras that happen not to be attached to the PC at
    the moment, which perhaps should be left alone, depending on the
    difficulty of reinstalling them.  The setting is:
        devmgr_show_nonpresent_devices=1

    To make this setting, it's not enough just to launch a command console
    and set it there, you have to do it in the environment settings
    themselves, so that the new setting will available to all running
    software, including Device Manager.  These instructions are correct for
    Win 7, but should also be close or identical for later versions.  It's certainly best, perhaps even necessary, to be signed on as the
    Administrator:
        <Rt-Click> My Computer/Computer
        Properties
        Advanced System Settings
        Advanced
        Environment Variables
        Choosing either ...
            Current User (preferably the Administrator)
            System
        ... click New and enter ...
            Variable name:  devmgr_show_nonpresent_devices
            Variable value: 1
        Click 'Ok' all the way out.

    As it's such a long time since I set this, I can't remember whether a
    reboot is required for it to be picked up, but logically I don't think
    it should be.

    Having done this, you can go into Device Manager and choose ...
        View, Devices by connection
        View, Show hidden devices
    ... and the first time you do this may be quite a shock if your OS has
    moved around a few times!

    The non-present devices are now more obvious by not being located in the
    main ACPI* device tree where mostly they would be, but note that
    software 'devices' and other pseudo 'devices' relating to services
    aren't going to be in the tree either, so absolutely do NOT, repeat NOT,
    just delete everything not in the ACPI* tree!  Also note that some of
    the off-tree devices have a faded icon, but again this alone is not
    enough of an identifier.

    Except that unfortunately from at latest Windows 10 this is no longer
    true. I think you probably still need the environment setting, I
    haven't tried it without, but choosing "Devices by connection" no longer
    offers you the substantially different view from the default that it did
    in former version of Windows up to and including at earliest 7. Now you
    have to go through each device category looking for the ones with faded
    icons :-(

    What you are looking for are devices with a faded icon that have
    counterparts of present devices within the ACPI* tree, which shows that
    that is where they really belong.  Those are the devices which were or
    are real, but currently are not present.  Switching between 'Devices by type' and 'Devices by connection' may be useful here.  If a device
    appears in the former with a faded icon alongside devices with a normal
    icon, and appears in the latter off the ACPI* tree, then most probably
    it's just the sort of thing you are looking for.  It's up to you whether
    you choose to delete anything like USB devices that happen not to be
    attached to the PC at the moment  -  I tend to leave things like
    scanners, phones, cameras, alone, but delete USB drives, as otherwise
    they clutter the view so much, but that's a personal choice.  What you should most probably do is uninstall non-present system devices such a Processors, Real-Time Clocks, Hard-disk controllers, etc, as they will
    have come from previous hardware the OS was on.

    There *used* to be a much faster way to remove old hardware from an
    image, using, IMS, an MS supplied program called DevCon.exe.  By giving
    it different command lines and logging and comparing the output of each,
    you could subtract the present devices from the total devices and so
    have a list of those non-present, and then uninstall any appropriate
    items from that, but this was in the days of W2k and possible XP.  I'm
    not aware of anything more modern which is as useful as that, but
    perhaps others may be able to make suggestions.


    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)