upgrade windows 7 32 to 64 - settings migrate

[reuah]

onboard windows migrate settings tools seems to make no clear distinction between settings and files, so I end up with gbs of data.

Is there a surer way to take along all the possible system settings to a new machine with 64 windows architecture?

[Q91]

64-bit is basicly a new installment since they dont share every DLL with eachother

[Erratic]

You cant use 32bit settings on 64bit but u can try and copy AppData folder coz some or most programs settings will work this is what i did when i got 64bit Win 7 but the best way would be to Install win 64bit then set your pc the way you want and then just use Acronis and keep regular back-ups

[Kingfish]

Windows easy transfer.

[reuah]

Okay, so here I start windows easy transfer. there are pictures, documents, program settings, all of which I exclude, and there are also windows settings (33mb) which I tick and other items (16gb) - untickable.
So to get rid of them you need to switch to advanced. Now, as explorer opens, I untick all - that was the trick. Now it is only windows settings which are to be backed up. And these - I presume from your posts - are exactly what can not be migrated, yes?

[-nelly-]

It's not an exact science. You keep what you want. You delete what you don't. You defrag the HDD. Then you do as Kingfish outlined above.

Once you've done it. Check all your cracked software as your doing this upgrade via M$ as more than likely anything cracked/patched will be reverted to OEM

[shirepirate]

windows settings (reg entries, system config data and user account settings) can be migrated from 32-bit 7 to 64-bit 7 in the manner you've described. it could even be done manually if one knows what they're doing.

[-nelly-]

All the above are correct with a lot of variables. If any variable moves. Your "move" is corrupt. Image what you want.

Then apply that image to the HDD. And as i've said. M$ will corrupt any crack/patch etc which you transfer by slipping in a .dll during the transfer/imaging.

Use CloneZilla to cast the O/S once you have all as you want it

---

Always have x86(x32bit) and x64bit images to fall back on