7 réponses
Hello,
Neither more nor less than the entire competition: at best useless, at worst dangerous.
Contrary to a commonly held belief, there is no way to compress the registry or to "speed it up."
The only benefit seems to be finding remnants of poorly uninstalled software, but that task can easily be done manually without any issues.
This kind of software will always crash on us.
We will be happy because it will bring us hundreds of language localization files that we don't use, and a bit less happy when it tries to mess with entries or DLLs that, for example, are not used because they relate to an external device that is currently not connected.
Neither more nor less than the entire competition: at best useless, at worst dangerous.
Contrary to a commonly held belief, there is no way to compress the registry or to "speed it up."
The only benefit seems to be finding remnants of poorly uninstalled software, but that task can easily be done manually without any issues.
This kind of software will always crash on us.
We will be happy because it will bring us hundreds of language localization files that we don't use, and a bit less happy when it tries to mess with entries or DLLs that, for example, are not used because they relate to an external device that is currently not connected.
Thank you for this response; but not wanting to tinker with "regedit", which log should I refer to instead?
The best solution is surely to refrain.
I find it more appropriate to focus on the unprompted launches of software (or other executables) and services, for example using Autoruns and Process Explorer, those two:
https://docs.microsoft.com/en-us/sysinternals/downloads/
In the presence of an unprompted or orphan process, the registry path is indicated.
If one is not satisfied with just killing the culprit, the name is provided, and one can look it up in the registry to directly find the relevant keys.
Or why not, but just for that as I said, use one of those famous registry utilities, but only to detect the keys that we previously highlighted.
I find it more appropriate to focus on the unprompted launches of software (or other executables) and services, for example using Autoruns and Process Explorer, those two:
https://docs.microsoft.com/en-us/sysinternals/downloads/
In the presence of an unprompted or orphan process, the registry path is indicated.
If one is not satisfied with just killing the culprit, the name is provided, and one can look it up in the registry to directly find the relevant keys.
Or why not, but just for that as I said, use one of those famous registry utilities, but only to detect the keys that we previously highlighted.
I miscommunicated; Autoruns and Process Explorer launch upon session opening or connection, independently of our will (unless we disable them from startup... although I have some recurring offenders in my task manager... thanks, Windows).
For example: Photos, Your Phone, Windows Health Security...
For example: Photos, Your Phone, Windows Health Security...
No, we are not talking about the same thing.
Services start automatically or executables are launched automatically at startup.
Aside from manually configuring services in services.msc, Autoruns and Process Explorer do not point out these events but are utilities specifically designed to disable what we don't need at startup or automatically.
Apart from this cleanup, I forgot Revo Uninstaller, which is very popular here, and users claim it does a better job of handling leftover software to uninstall.
Services start automatically or executables are launched automatically at startup.
Aside from manually configuring services in services.msc, Autoruns and Process Explorer do not point out these events but are utilities specifically designed to disable what we don't need at startup or automatically.
Apart from this cleanup, I forgot Revo Uninstaller, which is very popular here, and users claim it does a better job of handling leftover software to uninstall.