Windows XP SP3 Pro.[snip]
Windows KEY+PAUSE/BREAK
Click on hardware --> hardware manager:
//
MMC could not create the snap-in
The snap-in might have not been installed correctly
I've tried all the M$ "official" suggestions:
Regsvr32 Msxml.dll - No errors
Regsvr32 Msxml2.dll - No errors
Regsvr32 Msxml3.dll - No errors
Turned on plug and play
sfc /scannow - No errors
and rebooted lots of times
All my other snap-ins work fine.
Hardware manager worked fine about a week ago. Even tried loading a
saved registry from a month ago. Nothing worked.
Any ideas?
Shadow wrote:
Windows XP SP3 Pro.[snip]
Windows KEY+PAUSE/BREAK
Click on hardware --> hardware manager:
//
MMC could not create the snap-in
The snap-in might have not been installed correctly
I've tried all the M$ "official" suggestions:
Regsvr32 Msxml.dll - No errors
Regsvr32 Msxml2.dll - No errors
Regsvr32 Msxml3.dll - No errors
Turned on plug and play
sfc /scannow - No errors
and rebooted lots of times
All my other snap-ins work fine.
Hardware manager worked fine about a week ago. Even tried loading a
saved registry from a month ago. Nothing worked.
Any ideas?
What happens if you run devmgmt.msc?
Have you run virus scan, just in case?
On Sat, 27 Jan 2024 05:24:56 -0000 (UTC), "Auric__"[snip]
What happens if you run devmgmt.msc?
Same message as clicking on Device Manager.
When I open MMC and try to add devmgmt, it's the only one
without an icon. All the others have icons and work.
<https://postimg.cc/jCnj84JL>
If I click on it, it says it "cannot be started".
I must be missing a file, but filemon does not show what it
is. No relevant "NOT FOUND".
Eventvwr --> no relevant messages.
Have you run virus scan, just in case?
No malware.
Only things introduced to my system were three 128GB
pendrives(brand new Kingston Datatravellers). I traced them, but they
only altered the usual registry keys(mount points and classes).
And Uwe Sieber's latest USB Device Info/Tree Viewer. Which I
trust, but scanned on Jotti "just in case".
I use XP for Usenet and games. Linux for just about anything
else.
Shadow wrote:
On Sat, 27 Jan 2024 05:24:56 -0000 (UTC), "Auric__"[snip]
What happens if you run devmgmt.msc?
Same message as clicking on Device Manager.
When I open MMC and try to add devmgmt, it's the only one
without an icon. All the others have icons and work.
<https://postimg.cc/jCnj84JL>
If I click on it, it says it "cannot be started".
I must be missing a file, but filemon does not show what it
is. No relevant "NOT FOUND".
Eventvwr --> no relevant messages.
It sounds like the .msc file is the problem. I would extract a new copy from >the install media and see if that fixes it.
On Sat, 27 Jan 2024 16:00:06 -0000 (UTC), "Auric__" <not.my.real@email.address> wrote:
Shadow wrote:
On Sat, 27 Jan 2024 05:24:56 -0000 (UTC), "Auric__"[snip]
What happens if you run devmgmt.msc?
Same message as clicking on Device Manager.
When I open MMC and try to add devmgmt, it's the only one
without an icon. All the others have icons and work.
<https://postimg.cc/jCnj84JL>
If I click on it, it says it "cannot be started".
I must be missing a file, but filemon does not show what it
is. No relevant "NOT FOUND".
Eventvwr --> no relevant messages.
<slight snip>
It sounds like the .msc file is the problem. I would extract a new copy >>from the install media and see if that fixes it.
Extracted:
Name: devmgmt.msc
Size: 31.96kB (32,724 bytes)
Type: XML 1.0 document, ASCII text, with CRLF line terminators
MD5: 2dd6a1e73d1f9ae7d73df5ad82a7c9aa
SHA1: e85748814b593a056e5619cbbdedb82fd607bae1
Status: Scan finished. 0/14 scanners reported malware.
Scan taken on: January 27, 2024 at 8:07:28 PM GMT+1
Same checksums as the one in /windows/system32
Not sure if it's relevant, but my c:\documents and settings/username/appdata/Microsoft contains an empty folder called
devmgmt. Should it contain anything?
The same folder contains one called MMC with 3 entries:
secpol, mscorcfg and dfrg, all rather hefty UTF-8 encoded text files.
Shadow wrote:
On Sat, 27 Jan 2024 16:00:06 -0000 (UTC), "Auric__"
<not.my.real@email.address> wrote:
Shadow wrote:
On Sat, 27 Jan 2024 05:24:56 -0000 (UTC), "Auric__"[snip]
What happens if you run devmgmt.msc?
Same message as clicking on Device Manager.
When I open MMC and try to add devmgmt, it's the only one
without an icon. All the others have icons and work.
<https://postimg.cc/jCnj84JL>
If I click on it, it says it "cannot be started".
I must be missing a file, but filemon does not show what it
is. No relevant "NOT FOUND".
Eventvwr --> no relevant messages.
<slight snip>
It sounds like the .msc file is the problem. I would extract a new copy >>>from the install media and see if that fixes it.
Extracted:
Name: devmgmt.msc
Size: 31.96kB (32,724 bytes)
Type: XML 1.0 document, ASCII text, with CRLF line terminators
MD5: 2dd6a1e73d1f9ae7d73df5ad82a7c9aa
SHA1: e85748814b593a056e5619cbbdedb82fd607bae1
Status: Scan finished. 0/14 scanners reported malware.
Scan taken on: January 27, 2024 at 8:07:28 PM GMT+1
Same checksums as the one in /windows/system32
...huh.
Not sure if it's relevant, but my c:\documents and
settings/username/appdata/Microsoft contains an empty folder called
devmgmt. Should it contain anything?
I don't have that folder, even with devmgmt.msc open.
The same folder contains one called MMC with 3 entries:
secpol, mscorcfg and dfrg, all rather hefty UTF-8 encoded text files.
My %APPDATA%\MMC folder is empty, even with MMC running.
What I would do is delete %APPDATA%\devmgmt, and *MOVE* those text files out >of %APPDATA%\MMC -- put them on your desktop. Then retry devmgmt and see
what you get.
It sounds like the .msc file is the problem. I would extract a new copy
from the install media and see if that fixes it.
Extracted:
Name: devmgmt.msc
Size: 31.96kB (32,724 bytes)
Type: XML 1.0 document, ASCII text, with CRLF line terminators
MD5: 2dd6a1e73d1f9ae7d73df5ad82a7c9aa
SHA1: e85748814b593a056e5619cbbdedb82fd607bae1
Status: Scan finished. 0/14 scanners reported malware.
Scan taken on: January 27, 2024 at 8:07:28 PM GMT+1
Same checksums as the one in /windows/system32
Not sure if it's relevant, but my c:\documents and settings/username/appdata/Microsoft contains an empty folder called
devmgmt. Should it contain anything?
The same folder contains one called MMC with 3 entries:
secpol, mscorcfg and dfrg, all rather hefty UTF-8 encoded text files.
TIA
[]'s
Hello Sh!
** On Saturday 27.01.24 - 14:19, Sh wrote to :
It sounds like the .msc file is the problem. I would extract a new copy
from the install media and see if that fixes it.
Extracted:
Name: devmgmt.msc
Size: 31.96kB (32,724 bytes)
Type: XML 1.0 document, ASCII text, with CRLF line terminators
MD5: 2dd6a1e73d1f9ae7d73df5ad82a7c9aa
SHA1: e85748814b593a056e5619cbbdedb82fd607bae1
Status: Scan finished. 0/14 scanners reported malware.
Scan taken on: January 27, 2024 at 8:07:28 PM GMT+1
Same checksums as the one in /windows/system32
Mine is..
Directory of C:\WINDOWS\system32
03/31/2003 07:00 AM 33,079 devmgmt.msc
C:\WINDOWS\system32>fciv -both devmgmt.msc
//
// File Checksum Integrity Verifier version 2.05.
//
MD5
--------------------------------
36f28a9f92b0c5940898b6ea34381f30
SHA-1·
---------------------------------------- >6d2a6e4a1293ce482991f2ce397493dd03d9dd78
Not sure if it's relevant, but my c:\documents and
settings/username/appdata/Microsoft contains an empty folder called
devmgmt. Should it contain anything?
The same folder contains one called MMC with 3 entries:
secpol, mscorcfg and dfrg, all rather hefty UTF-8 encoded text files.
TIA
[]'s
No emtpy devmgmt dir here.
On Sat, 27 Jan 2024 19:54:52 -0000 (UTC), "Auric__" <not.my.real@email.address> wrote:[snip]
What I would do is delete %APPDATA%\devmgmt, and *MOVE* those text files >>out of %APPDATA%\MMC -- put them on your desktop. Then retry devmgmt and >>see what you get.
OK. Done. Same error message.
Running out of ideas...
This is the first time I've "lost" my device manager in over 2
decades.
Google is *NEVER* friendly when you really need it. And M$
treats XP like it was a contagious disease.
PS I'll try rebooting into safe mode and running it. Maybe a
driver or service is conflicting somehow. Maybe tomorrow. Have stuff
to do.
Shadow wrote:
On Sat, 27 Jan 2024 19:54:52 -0000 (UTC), "Auric__"[snip]
<not.my.real@email.address> wrote:
What I would do is delete %APPDATA%\devmgmt, and *MOVE* those text files >>>out of %APPDATA%\MMC -- put them on your desktop. Then retry devmgmt and >>>see what you get.
OK. Done. Same error message.
Running out of ideas...
This is the first time I've "lost" my device manager in over 2
decades.
Google is *NEVER* friendly when you really need it. And M$
treats XP like it was a contagious disease.
I hate to say it, but in today's world, XP connected to the internet *is* an >infectious disease.
PS I'll try rebooting into safe mode and running it. Maybe a
driver or service is conflicting somehow. Maybe tomorrow. Have stuff
to do.
That's certainly possible. Or some program running in the background or >something. Just remember: If all else fails, reinstalling Windows generally >fixes anything except hardware failure. It sucks, but before Win7 I generally >reinstalled 2-3 time per year.
On an unrelated side note, please do me a favor and add a space after your >sig delimiter. "-- " and not "--". Newsreaders generally can recognize the >form with the space and automatically remove it from replies; Xnews (at >least) doesn't recognize the version without the space.
Shadow wrote:
On Sat, 27 Jan 2024 19:54:52 -0000 (UTC), "Auric__"[snip]
<not.my.real@email.address> wrote:
What I would do is delete %APPDATA%\devmgmt, and *MOVE* those text files >>> out of %APPDATA%\MMC -- put them on your desktop. Then retry devmgmt and >>> see what you get.
OK. Done. Same error message.
Running out of ideas...
This is the first time I've "lost" my device manager in over 2
decades.
Google is *NEVER* friendly when you really need it. And M$
treats XP like it was a contagious disease.
I hate to say it, but in today's world, XP connected to the internet *is* an infectious disease.
PS I'll try rebooting into safe mode and running it. Maybe a
driver or service is conflicting somehow. Maybe tomorrow. Have stuff
to do.
That's certainly possible. Or some program running in the background or something. Just remember: If all else fails, reinstalling Windows generally fixes anything except hardware failure. It sucks, but before Win7 I generally reinstalled 2-3 time per year.
On an unrelated side note, please do me a favor and add a space after your sig delimiter. "-- " and not "--". Newsreaders generally can recognize the form with the space and automatically remove it from replies; Xnews (at least) doesn't recognize the version without the space.
Tssk.... My XP PRO works fine, and devmgmt
started in a dos box, works quite well.......
Shadow wrote:
On Sat, 27 Jan 2024 19:54:52 -0000 (UTC), "Auric__" <not.my.real@email.address> wrote:[snip]
What I would do is delete %APPDATA%\devmgmt, and *MOVE* those text files >>out of %APPDATA%\MMC -- put them on your desktop. Then retry devmgmt and >>see what you get.
OK. Done. Same error message.
Running out of ideas...
This is the first time I've "lost" my device manager in over 2 decades.
Google is *NEVER* friendly when you really need it. And M$
treats XP like it was a contagious disease.
I hate to say it, but in today's world, XP connected to the internet *is* an infectious disease.
PS I'll try rebooting into safe mode and running it. Maybe a
driver or service is conflicting somehow. Maybe tomorrow. Have stuff
to do.
That's certainly possible. Or some program running in the background or something. Just remember: If all else fails, reinstalling Windows generally fixes anything except hardware failure. It sucks, but before Win7 I generally reinstalled 2-3 time per year.
On an unrelated side note, please do me a favor and add a space after your sig delimiter. "-- " and not "--". Newsreaders generally can recognize the form with the space and automatically remove it from replies; Xnews (at least) doesn't recognize the version without the space.
--
Sometimes the hardest thing to believe is the truth.
On Mon, 29 Jan 2024 20:16:17 -0000 (UTC)[snip]
"Auric__" <not.my.real@email.address> wrote:
I hate to say it, but in today's world, XP connected to the internet *is*
an infectious disease.
Steady, now. This *is* an XP NG!
Kerr-Mudd, John wrote:
On Mon, 29 Jan 2024 20:16:17 -0000 (UTC)[snip]
"Auric__" <not.my.real@email.address> wrote:
I hate to say it, but in today's world, XP connected to the internet *is* >>> an infectious disease.
Steady, now. This *is* an XP NG!
Yeah, but I think we all know that XP was never all that great with security, and now with almost 10 years out of support, putting an XP box on the internet without some sort of mitigating factor is just begging to make it a biohazard box.
I hate to say it, but in today's world, XP connected to the internet
*is* an infectious disease.
Steady, now. This *is* an XP NG!
John,
I hate to say it, but in today's world, XP connected to the internet
*is* an infectious disease.
Steady, now. This *is* an XP NG!
Meh, don't worry about it.
I've been reading that kind of FUD forever, always about the previous
Windows version whenever a new one came out, but have never heard about
a single outbreak that was tracked back to XP itself mucking up - any
more than Win7, Win8, Win10 or Win11 did/do that.
I've been using XP for at least the last 15 years, and have never
experienced it to be(coming) any kind of "an infectious disease". And
that without it running any kind of AV product ever (other than the one
I've got loaded into my wet-ware :-) ).
And oh yeah, for over a decade I oversaw a room full of XP machines,
used by kids. Never have seen them get ill or infectious by themselves either.
The funny thing is that most people looking down on older Windows
versions seem to have zero problem with their machines being on a
continuous, weekly drip of regular and security updates. Personally, if
I would know a human who would need that kind of TLC I would consider
them to be quite ill ...
R.Wieser wrote:
I've been reading that kind of FUD forever, always about the previous
Windows version whenever a new one came out, but have never heard about
a single outbreak that was tracked back to XP itself mucking up - any
more than Win7, Win8, Win10 or Win11 did/do that.
It's not intended to be fud. XP doesn't receive security updates any more so >if a new vulnerability is found, MS will just say "That's nice, we told you >so."
I managed to fix the problem, partially. I simply deleted the
"Hardware Manager" Snapin key.
// [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{74246bfc-4c96-11d0-abef-0020af6b0b7a}]
//
Now WinKey+PAUSE/BREAK ---> Hardware --> Hardware manager
brings up my hardware manager again.
I didn't even need to reboot.
On the downside, hardware manager no longer appears as a
snap-in option for the MMC console. Not that I ever used that much.
TY all for the attempted help.
[]'s
It's not intended to be fud. XP doesn't receive security updates
any more
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime.
Do you really think there aren't any more undiscovered and/or
unreported?
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime. Do you really think there aren't any more
undiscovered and/or unreported?
Then count yourself lucky.
I cannot tell you the number of times I've had client machines
that were "mysteriously" infected.
(Yes, stupid people do stupid things. Not the point.)
That "continuous, weekly drip" means that MS is fixing issues.
If you find an issue with XP, your choices are fix it yourself, or pay someone else to do it for you, or else do nothing and just live with it.
On Wed, 31 Jan 2024 15:38:10 -0300
Shadow <Sh@dow.br> wrote:
[]
I managed to fix the problem, partially. I simply deleted the
"Hardware Manager" Snapin key.
//
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{74246bfc-4c96-11d0-abef-0020af6b0b7a}]
//
Now WinKey+PAUSE/BREAK ---> Hardware --> Hardware manager
brings up my hardware manager again.
On my box (XP3SP3)
WinKey+PAUSE/BREAK gives 'System Properties' Box, chosing "Hardware' tab
I have 'Device Manager', not 'Hardware Manager'
Using regeditx I navigated to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns >\{74246bfc-4c96-11d0-abef-0020af6b0b7a}
Exporting that key I get
------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns >\{74246bfc-4c96-11d0-abef-0020af6b0b7a}] "NameStringIndirect"="@C:\\WINDOWS >\\system32\\devmgr.dll,-5" "NameString"="Device Manager" >"Provider"="Microsoft Corporation"
"Version"="1.0"
"About"="{94abaf2a-892a-11d1-bbc4-00a0c90640bf}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns >\{74246bfc-4c96-11d0-abef-0020af6b0b7a}\StandAlone]
------------------
--I didn't even need to reboot.
On the downside, hardware manager no longer appears as a
snap-in option for the MMC console. Not that I ever used that much.
TY all for the attempted help.
[]'s
Auric,
It's not intended to be fud. XP doesn't receive security updates
any more
Yes, and ? Neither does Win7 or Win8, but you still use the former.
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime.
for which it, over its lifetime, got security updates. I could argue
that XP is better off security wise than Win11 is, as thats has got just
a few years of them.
Do you really think there aren't any more undiscovered and/or
unreported?
And that differs for XP in regard to Win7, win8, win10 and win11 ... how exactly ?
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime. Do you really think there aren't any more
undiscovered and/or unreported?
Again, you're singling XP out for problems that exist in all Windows versions.
Mind you, you where trying to tell us that XP is .. how did you put it
... "an infectious disease". Currently all I see you post is FUD that
is applicable to all Windows versions.
Then count yourself lucky.
No, I don't. Not with more than a decade of kids working on XP
computers and having zero problems with it. Besides my own 'puter which
I've been using for 15+ years.
I cannot tell you the number of times I've had client machines
that were "mysteriously" infected.
I could counter that with people who "did nothing" with/on their
computers before it went all bad, only to discover that they did plenty,
but conveniently forgot all about having done it - even if they did it
just hours before.
(Yes, stupid people do stupid things. Not the point.)
Actually, yes, it is. With it you're telling me that its (most always)
the user which is the cause of the puter becoming "an infectious
disease" - not the OS itself.
That "continuous, weekly drip" means that MS is fixing issues.
To me it means that that new version of Windows has got a gazillion of security holes, and MS is playing whack-a-mole, hoping that they can
plug a hole before it gets exploited.
In comparision any version that has been EOL-ed after having gotten
security updates upto that point (like XP and your Win7) must be much
more secure, don't you agree ?
If you find an issue with XP, your choices are fix it yourself, or pay
someone else to do it for you, or else do nothing and just live with
it.
Which is true for any EOL-ed version (and often even for non-EOL-ed versions). Again, nothing XP specific.
And thats ofcourse beside the issues that are never fixed because of
"works as intended, not a bug" ones, which you always have to deal with
(or work around) yourself.
Bottom line, you've been claiming that XP connected to the internet is
"an infectious disease", but I've not seen you support that stance
anywhere.
Auric,
It's not intended to be fud. XP doesn't receive security updates
any more
Yes, and ? Neither does Win7 or Win8, but you still use the former.
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime.
for which it, over its lifetime, got security updates. I could argue that
XP is better off security wise than Win11 is, as thats has got just a few >years of them.
Do you really think there aren't any more undiscovered and/or
unreported?
And that differs for XP in regard to Win7, win8, win10 and win11 ... how >exactly ?
Also, let's not forget the sheer number of issues that were uncovered
during XP's lifetime. Do you really think there aren't any more
undiscovered and/or unreported?
Again, you're singling XP out for problems that exist in all Windows >versions.
Mind you, you where trying to tell us that XP is .. how did you put it ... >"an infectious disease". Currently all I see you post is FUD that is >applicable to all Windows versions.
Then count yourself lucky.
No, I don't. Not with more than a decade of kids working on XP computers
and having zero problems with it. Besides my own 'puter which I've been
using for 15+ years.
I cannot tell you the number of times I've had client machines
that were "mysteriously" infected.
I could counter that with people who "did nothing" with/on their computers >before it went all bad, only to discover that they did plenty, but >conveniently forgot all about having done it - even if they did it just
hours before.
(Yes, stupid people do stupid things. Not the point.)
Actually, yes, it is. With it you're telling me that its (most always) the >user which is the cause of the puter becoming "an infectious disease" - not >the OS itself.
That "continuous, weekly drip" means that MS is fixing issues.
To me it means that that new version of Windows has got a gazillion of >security holes, and MS is playing whack-a-mole, hoping that they can plug a >hole before it gets exploited.
In comparision any version that has been EOL-ed after having gotten security >updates upto that point (like XP and your Win7) must be much more secure, >don't you agree ?
If you find an issue with XP, your choices are fix it yourself, or pay
someone else to do it for you, or else do nothing and just live with it.
Which is true for any EOL-ed version (and often even for non-EOL-ed >versions). Again, nothing XP specific.
And thats ofcourse beside the issues that are never fixed because of "works >as intended, not a bug" ones, which you always have to deal with (or work >around) yourself.
Bottom line, you've been claiming that XP connected to the internet is "an >infectious disease", but I've not seen you support that stance anywhere.
Regards,
Rudy Wieser
The only reason MS has tons more versions of Windows is because
they have to keep the $$$ coming in.
Toolwiz's Time Freeze is no longer available.
However, there are other programs which will do the same as Time
Freeze but they cost money.
It's not intended to be fud. XP doesn't receive security updates
any more
Yes, and ? Neither does Win7 or Win8, but you still use the former.
Under emulation. Without internet access. For testing only, not
day-to-day use.
I don't use 11 outside of testing so I can't really speak to that,
but any system that currently receives bugfixes and security patches
scores higher in my book than one which doesn't.
Mind you, you where trying to tell us that XP is .. how did you put
it ... "an infectious disease". Currently all I see you post is FUD
that is applicable to all Windows versions.
You misread it. I didn't say that XP is a disease, I said that
"XP connected to the internet is an infectious disease."
Do you really think there aren't any more undiscovered and/or
unreported?
And that differs for XP in regard to Win7, win8, win10 and win11 ...
how exactly ?
If they get discovered on 10 or 11 they get fixed. Previous systems,
not so much.
Look into how many issues XP had during its lifetime. What do you think
would have happened if MS hadn't played "whack-a-mole" with XP?
In comparision any version that has been EOL-ed after having
gotten security updates upto that point (like XP and your Win7)
must be much more secure, don't you agree ?
No. And again, please reread, I switched to 10 the day 7 EOL'd.
(Well, I did Linux for a little while, but Windows works better
for my day-to-day desktop usage.)
Bottom line, you've been claiming that XP connected to the internet
is "an infectious disease", but I've not seen you support that stance
anywhere.
Shrug. Fine. You do you. If I'm using Windows online, it's going to be
a system that's kept current.
On Wed, 31 Jan 2024 19:44:07 +0000, "Kerr-Mudd, John"
<admin@127.0.0.1> wrote:
On Wed, 31 Jan 2024 15:38:10 -0300
Shadow <Sh@dow.br> wrote:
[]
I managed to fix the problem, partially. I simply deleted the
"Hardware Manager" Snapin key.
Since it referenced {94abaf2a-892a-11d1-bbc4-00a0c90640bf}
I deleted that key too:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns \{90087284-d6d6-11d0-8353-00a0c90640bf}]
"NameString"="Extensão do 'Gerenciador de dispositivos'" "Provider"="Microsoft Corporation"
"Version"="1.0"
"About"="{94abaf2a-892a-11d1-bbc4-00a0c90640bf}"
Notice, no ""NameStringIndirect". Which usually refers to a
.dll.
Is yours the same?
Auric,[]
But I see that you've again skirted what I said there : that you effectivily lied by omission, by singling out XP and ignoring that the same problem exists in every other version of Windows.
On Wed, 31 Jan 2024 18:39:41 -0300
Shadow <Sh@dow.br> wrote:
On Wed, 31 Jan 2024 19:44:07 +0000, "Kerr-Mudd, John"
<admin@127.0.0.1> wrote:
On Wed, 31 Jan 2024 15:38:10 -0300
Shadow <Sh@dow.br> wrote:
[]
I managed to fix the problem, partially. I simply deleted the
"Hardware Manager" Snapin key.
Since it referenced {94abaf2a-892a-11d1-bbc4-00a0c90640bf}
I deleted that key too:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns
\{90087284-d6d6-11d0-8353-00a0c90640bf}]
"NameString"="Extensão do 'Gerenciador de dispositivos'"
"Provider"="Microsoft Corporation"
"Version"="1.0"
"About"="{94abaf2a-892a-11d1-bbc4-00a0c90640bf}"
Notice, no ""NameStringIndirect". Which usually refers to a
.dll.
Is yours the same?
Barring the Portugese translation, yes
So it doesn't seem to be the registry at fault (or at least not these >entries).
Carson,
Toolwiz's Time Freeze is no longer available.
I can imagine that, as Windows (as far back as XP) has got a "time freeze" >method build-in - to make copying of a HD possible while the os is running >on, and modifying it.
Rudy Wieser
Carson,Del
I can imagine that, as Windows (as far back as XP) has got a "time
freeze" method build-in - to make copying of a HD possible while the
os is running on, and modifying it.
That is called making a backup.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 487 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 151:33:52 |
| Calls: | 9,660 |
| Calls today: | 2 |
| Files: | 13,709 |
| Messages: | 6,166,111 |