Good Idea to remove 32-Bit variants of the 64-Bit components?

[Mortadello]

Hey,

So I went ahead and removed all the exact copies of a component which were had "xyz - 32 Bit" and left the upper/above component "xyz" in tact, so far so so good, i could boot normally, with no errors but I witnessed that now i cannot use "chkdsk" tool for repairing drives and so xD

So would you guys say to better keep the - 32 Bit versions in tact?

 

[Mortadello]

this component for instance, had another sub-component attached to it (in green color) stating:
"Dateiauswahl-UI-Host - 32 Bit" and that, for one, I did remove, as many other similar ones.

 

[garlin]

In reality, most of the 32-bit components don't take up that much space. They exist for backwards compatibility, since some legacy or current user apps may be 32-bit executables.

Some users may never notice a problem, depending on which apps they run. But if you want to keep the best compatibility for apps, I would leave the 32-bit components whenever the same 64-bit version exists.

If you have a licensed copy of NTLite, you can always do a Host refresh and re-install any removed 32-bit components.
If you're using the free edition, you probably want to avoid doing a Windows re-install so it's better not to remove the components.

 

[Mortadello]

In reality, most of the 32-bit components don't take up that much space. They exist for backwards compatibility, since some legacy or current user apps may be 32-bit executables.

Some users may never notice a problem, depending on which apps they run. But if you want to keep the best compatibility for apps, I would leave the 32-bit components whenever the same 64-bit version exists.

If you have a licensed copy of NTLite, you can always do a Host refresh and re-install any removed 32-bit components.
If you're using the free edition, you probably want to avoid doing a Windows re-install so it's better not to remove the components.

yea okay makes sense, i think i will restore them via host refresh, i do not have apparent issues but as i said the chkdsk tool does not work now and you never know when yoiu need to run diagnostics or such and at that point it wont work is pretty bad.

thx