Mouse freezing

Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc /scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system, composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

On 03/11/2018 17:30, Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable.

Look your problem has been going on for nearly two weeks (I can see your
old posts here); Have you thought of biting the bullet and wiping your
HD and start again? It is a sign of stupidity to keep asking for help
when the problem lies in your ability to use a machine. Why don't you
use Linux or Apple MAC that has no such problems? Windows is for
intelligent people and you haven't shown any sign of intelligence in
you. Any sign I see is that you are a drop out from your school and so
you never completed any formal secondary education.

IT Technicians in Bangalore or Hyderabad can solve your problems within
10 minutes but you have always hated non white people. So now you
should do something else such as joining the racists in the Labour party
who are now investigated for hate crimes against the Jews!!!!.





--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc /scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system, composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete Appdata\Local\Packages\Microsoft.MicrosoftEdge,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

On Sat, 03 Nov 2018 17:30:08 +0000, Terry Pinnell
wrote:

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

Is the mouse cordless? If so try new batteries.

Steve
--
http://www.npsnn.com

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc /scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system, composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete Appdata\Local\Packages\Microsoft.MicrosoftEdge,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0&0000

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&0000

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

Stephen Wolstenholme wrote:

On Sat, 03 Nov 2018 17:30:08 +0000, Terry Pinnell
wrote:

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

Is the mouse cordless?
We must have been typing almost simultaneously.
From my last:
"It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G."

If so try new batteries.
First thing I checked. Then cleaned lens. Then tested different
surfaces. Then kicked desk...


Steve

Terry Pinnell wrote:

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc /scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system, composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete Appdata\Local\Packages\Microsoft.MicrosoftEdge,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0&000 0

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&0000

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

The Edge and mouse issues seem unlikely to be related IMO, as I think
you also implied, Paul. I'll stay in the one thread for now anyway. The
mouse is my main concern.

Re Edge, here's more forensics:
https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1

Terry, East Grinstead, UK

Terry Pinnell wrote:

Terry Pinnell wrote:

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc /scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system, composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete Appdata\Local\Packages\Microsoft.MicrosoftEdge,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0&00 00

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&0000

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

The Edge and mouse issues seem unlikely to be related IMO, as I think
you also implied, Paul. I'll stay in the one thread for now anyway. The
mouse is my main concern.

Re Edge, here's more forensics:
https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1

Terry, East Grinstead, UK

Happily, the mouse issue is fixed ;-)

It defied intuition but I tried changing the USB ports of both the
Logitech wireless unit and the Anker USB 'adapter' and with the current
combination I have a smooth mouse again.

The Edge issue remains as I expected. The current subject heading is
misleading so I'll repost.

Terry, East Grinstead, UK

"Terry Pinnell" wrote in message
...

Terry Pinnell wrote:

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc
/scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system,
composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete
Appdata\Local\Packages\Microsoft.MicrosoftEdg e,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0&00 00

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&0000

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

The Edge and mouse issues seem unlikely to be related IMO, as I think
you also implied, Paul. I'll stay in the one thread for now anyway. The
mouse is my main concern.

Re Edge, here's more forensics:
https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1

Terry, East Grinstead, UK
I had mouse (USB wired) freezing sometime after installing the 1809 Windows
Update.
What finally fixed it was, believe it or not, was uninstalling and
reinstalling my audio drivers.
I rebooted between doing those things. Later, I uninstalled and reinstalled
my mouse just on a whim.
Now, the problem is fixed. I really think it was my audio (sound card/chip}
drivers that were 'updated' during the 1809 install.
Try it, It takes little time to do and is free. Really nothing to lose.
--
Buffalo

"Buffalo" wrote:

"Terry Pinnell" wrote in message
.. .

Terry Pinnell wrote:

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc
/scannow
again.

I'm hoping that the application runtime error details from Event Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system,
composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete
Appdata\Local\Packages\Microsoft.MicrosoftEdge ,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0&0 000

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&0000

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

The Edge and mouse issues seem unlikely to be related IMO, as I think
you also implied, Paul. I'll stay in the one thread for now anyway. The
mouse is my main concern.

Re Edge, here's more forensics:
https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1

Terry, East Grinstead, UK
I had mouse (USB wired) freezing sometime after installing the 1809 Windows
Update.
What finally fixed it was, believe it or not, was uninstalling and
reinstalling my audio drivers.
I rebooted between doing those things. Later, I uninstalled and reinstalled
my mouse just on a whim.
Now, the problem is fixed. I really think it was my audio (sound card/chip}

drivers that were 'updated' during the 1809 install.
Try it, It takes little time to do and is free. Really nothing to lose.

Thanks. Our posts crossed in the digital ether. As you see from mine,
I've now solved it.

Terry, East Grinstead, UK

"Terry Pinnell" wrote in message
...

"Buffalo" wrote:

"Terry Pinnell" wrote in message
. ..

Terry Pinnell wrote:

Paul wrote:

Terry Pinnell wrote:
Despair!

I now have a new issue which makes the PC almost unusable. The mouse
cursor is freezing every few seconds and sometimes it takes me many
seconds to get it back. When I do it's jerky and sometimes
disappears.

The previous issues with the metro Apps and taskbar etc are still OK.
But I believe this new issue might be connected with the symptom that
I
cannot open Edge.

Event Viewer shows hundreds of identical application errors and this
seems to me the most likely cause.
https://www.dropbox.com/s/0bdfq21us5...ng-1.jpg?raw=1
https://www.dropbox.com/s/xyrg1jof4k...18-2.jpg?raw=1
(Those were just the one part of Event Viewer I looked at.)

I tried an SR without success. I tried disabling one of the two (??)
apparently identical entries in Device Mgr. And uninstalling it and
rebooting.
https://www.dropbox.com/s/un7yy6snhf...g-1a.jpg?raw=1

I tried that same Powershell command again. Naturally I did sfc
/scannow
again.

I'm hoping that the application runtime error details from Event
Viewer
will give the experts some ideas as to what might be the underlying
cause please.

(As an example of the impact of a virtually 'no mouse' system,
composing
this with the screenshots took nearly an hour.)

Terry, East Grinstead, UK

Device Manager:

Do you actually have three mice or HID devices ?

Look at each entry, look at Properties, HardwareID, see
if the hardware id is reasonable or not.

If you had one Unifying Receiver and three devices of some sort,
it's always possible you'd end up with three almost-identical looking
Device Manager entries.

On my current machine, which has one mouse, if I saw the three mice,
I would delete all three and let the system restore them when you
scan for hardware changes. Or, alternately, when you reboot.

*******

For the other issue, the 80070005 is probably a permissions issue of
some sort. But since it doesn't give any details, where to start ?

This article, has the user delete
Appdata\Local\Packages\Microsoft.MicrosoftEdg e,
then use "our favorite recipe" to put it back. And they do it this way,
because the in-box bit is likely set on MSEdge, so ordinary removal
will
not work.

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

But before you go off and do that, consider that what they're showing
("Appdata") means the code is installed on a "per-account" basis.

By simply creating a new temporary account, and running MSEdge from
there, you can first check to see whether "clean code" fixes the
problem.

The MSedge might be clean itself, but the "data" stored in the name
of edge, in your existing profile, might have a problem. And Windows
has archives now, so if you blow away the data, Windows puts the data
back by using an archive. I can't test for a "data" issue, using the
"new account" method.

But at least it would be a quick check, that a fix is possible at
the MSEdge level. And the problem isn't some other subsystem.

1) Try the new account test, test MSedge, check for Events.
2) Follow the WindowsClub recipe. The permissions on the directory
in question could be quite messy. There are a number of ways to
solve that.
3) I have no way of knowing whether data or extensions in MSEdge
(which might not be part of the binary package), are healthy
or not. It could still tip over after these steps.

HTH,
Paul

Thanks Paul.

I've installed an ancient optical mouse so I can at least work in this
Win 10 PC.

Leaving Edge aside for a while, I've dusted off my old PC and installed
the suspect mouse on it. I'm sort of disappointed to find that so far
it's working fine. A similar freezing issue would have meant I could
quickly replace the mouse. It's a preferred type I've been using for few
years, an Anker Ergonomic Wireless Vertical Mouse, model TM156G.

In XP Device Manager:
https://www.dropbox.com/s/1dm8wihbw4...XP-1.jpg?raw=1

The drivers for both entries are shown as identical
C:\WINDOWS\system32\DRIVERS\mouclass.sys
C:\WINDOWS\system32\DRIVERS\mouhid.sys

But the Details tab shows this:
XP First entry
HID\VID_046D&PID_C517&MI_01&COL01\7&46DCEF6&0& 0000

XP First entry
HID\VID_062A&PID_4102&COL01\8&35C19CB0&0&000 0

(I don't have Dropbox on XP - they stopped supporting it - so I couldn't
compose posts with screenshots comfortably from there.)

In Win 10 Device Manager the screenshot I posted previously showed an
additional entry (the first one). That supports my 3D Connexion Space
Navigator (which I use in Google Earth). The other two were similar to
the two in my XP screenshot. In Win 10's Device Manager NOW, there's a
fourth entry, 'Microsoft USB lntelliMouse Optical', allowing me to work
with this old mouse.


Later...

Terry, East Grinstead, UK

The Edge and mouse issues seem unlikely to be related IMO, as I think
you also implied, Paul. I'll stay in the one thread for now anyway. The
mouse is my main concern.

Re Edge, here's more forensics:
https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1

Terry, East Grinstead, UK
I had mouse (USB wired) freezing sometime after installing the 1809
Windows
Update.
What finally fixed it was, believe it or not, was uninstalling and
reinstalling my audio drivers.
I rebooted between doing those things. Later, I uninstalled and
reinstalled
my mouse just on a whim.
Now, the problem is fixed. I really think it was my audio (sound
card/chip}

drivers that were 'updated' during the 1809 install.
Try it, It takes little time to do and is free. Really nothing to lose.

Thanks. Our posts crossed in the digital ether. As you see from mine,
I've now solved it.

Terry, East Grinstead, UK

I also tried using a different USB port (both USB 3 and USB 2) and it
worked, for awhile, a day or so, I believe, and then the problem came back.
Not sure if audio drivers can affect USB ports or ?
So, if the problem returns, try what I did.
Best of luck,
--
Buffalo