Hi,
I have a brand new computer, but an HP technical support guy made a mistake and gave me a totally wrong solution to a recent problem, telling me to run the command "regsvr32 msxml3.dll"
Did that command change anything in my computer or its operating system (Win 7, 64-bit)? If so, how can I reverse the change without doing system restore?
Thanks!
You say that you have enlisted HP Technical Support already for this problem & are not happy with the "wrong solution" provided.
I suggest you return to them to seek further advice.
Presumably this new computer is under Warranty.
As such a duty of care applies.
Before I came here looking for your good people's help, I already called HP technical support again after I found the official Windows 7 solution to my error code, which revealed that the HP technical support guy gave me a wrong solution, but they were not able to give me any information on whether this command changed anything in my operating system. They just told me to ask Microsoft. But I can't ask Microsoft because there is no free service to do that.
Can anyone here share your knowledge of this command with me?
All that command does is register the .dll as installed in the system.
This is usually done if that .dll is no longer recognized and registering it will fix the problem.
Registering a .dll that is already working will cause no problems.
Explanation of Regsvr32 usage and error messages
Hi pbcopter,
Thanks for your reply. As I am a novice, though, may I just clarify: is the msxml3.dll supposed to be, by design, in "unregistered" status or "registered" status on a Windows 7 64-bit system? I don't want something that is supposed to be "unregistered" to now be "registered".
The HP tech support guy had accidentally looked at a forum user's suggestion about a Windows VISTA operating system, so is the status of msxml3.dll in VISTA different by design from its status in Win 7 x 64 -- for example, registered vs. unregistered or active vs. inactive/ dormant ?
Thanks again!
As far as I'm aware of, no .dll is designed to be unregistered, if it is native to the OS. Unregistered .dlls may cause problems with programs or functions that are designed to use them. There are programs that do not require installing, thus I don't believe that they are entered into the registry, and I suppose that they may have .dlls within them that remain unregistered, but that is simply a guess. As stated previously, registering a .dll shouldn't cause any harm.
Can you give us some information on the original problem and what you are seeing now as we may be able to find the answers for you?
Hi Niemiro,
Thanks. Finally the critical info :) (But you would be wrong in assuming my computer is as good as new. This was but one problem among many that it has.)
And thanks to everyone else too for your input.
Quote