Of course not needing fixes at all would certainly be ideal, but arguably isn't realistic. But given that it seems fairly unlikely to cause conflicts with other applications or services on my system and it's only consuming 4 MB of RAM out of my 32 GB installed, it isn't enough for me to worry about, personally.Ĭlick to expand.I'd certainly rather have quick fixes than delayed fixes. I don't know exactly what the UI Watcher does, and therefore don't know what the ramifications of preventing it would be. The gratification of having finally solved the problem was rather offset by the knowledge that I had no one but myself to blame for having to suffer the problem in the first place. I've had a few too many times where I tinkered with something and didn't notice adverse consequences until later, by which point I'd sort of forgotten about my tinkering - so I ended up losing a bunch of time and hair troubleshooting the issue before I finally remembered that one tweak that sounded like such a good idea at the time, and which turned out to be the underlying cause of the problem I didn't encounter until later. I get an fully support the concept of keeping your system as simple as possible to meet your needs, but I would argue that disabling things via mechanisms that the vendor does not support or recommend is ADDING complexity, not reducing it - especially if you don't have a clear understanding of what the component does or what the ramifications of disabling it would be.
I ended up pointing them to a Microsoft utility that can purge all references to an application from the Windows Installer database, which did allow a new Reflect 64-bit installation to proceed, but that's obviously messy.Ĭlick to expand.Not sure what it does, but on my system it consumes 0% CPU and 4 MB of RAM, so I personally wouldn't consider tinkering with it to be a favorable risk/reward proposition. Both of those activities resulted in error messages.
The result was that not only did Reflect refuse to work, but the user also wasn't able to install Reflect 64-bit over it or uninstall the existing Reflect application. Basically, they used some tool to migrate Reflect 32-bit over to 64-bit Windows. Apparently there are utilities that will try to do that for you, but I only know that because somebody posted in the Macrium forums about problems they encountered after they tried that. As for migrating the application themselves, I wouldn't recommend that.
Better yet would be to link your old PC's Windows license to your Microsoft account, in which case you could choose to reassign that license to your new PC, but that isn't always an option depending on how your old PC received its Windows license - and some people don't want to link their Window logon to their Microsoft account, which is required for that mechanism.Ī 32-bit Windows image is of no real use when setting up a 64-bit system, except that you can of course retrieve your personal data out of it, and then some application config files, depending on the application. Pro) as the image you would be ReDeploying onto it. For best chance of success there, make sure your new PC comes with a license for the same edition of Windows (Home vs. The only potential snag there is Windows activation.
Maybe that finally I will stay with a new 64-bit system to avoid such difficulties.Ĭlick to expand.I would confirm whether 32-bit drivers are available for all of your new system's hardware before even attempting that process, but if the drivers exist and you were willing to continue operating on no more than 4GB of RAM, then yes in theory the process you describe should work - and you would indeed still have the option to restore the 64-bit installation (or just perform a fresh install). Is my assumption correct that an image created of a 32-bit system is of no use in case that I want to continue with a 64-bit system? Or are there any parts (or whatever) of the image which could be useful when performing the setup of the 64-bit system? I restore "Image 1" bringing back the new PC in its original condition (and afterwards I set up all my programs etc. as described in your posting) I go to step 3:ģ. If then all works fine I stay with this solution.
I transfer (on a trial basis) my old 32-bit system to the new PC by using the feature "ReDeploy Restored Image to new hardware" of Macrium's Home Edition (-> the bare metal restore). I buy a new PC (64-bit) and create immediately an image of its disk (that means before installing or changing anything) ("Image 1").Ģ. Maybe that finally I will stay with a new 64-bit system to avoid such difficulties.īut would the following be a (technically) feasible procedure?ġ. Click to expand.Thanks for your explanations, jphughan.