NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bgrumbin
Aug 05, 2019Aspirant
AT&T BEAM device =KILLS= my mouse in Windows 10
My problem is that the AT&T BEAM device (identifies itself only with the brand name NETGEAR on the device) =KILLS= my mouse when I attach it to my new Windows 10 computer making the computer and airc...
bgrumbin
Aug 13, 2019Aspirant
It is a wired mouse and there have never been any problems connecting the BEAM to my Windows 7 set of computers, only the brand new still being developed Windows 10. It is a quite important problem for me because my DSL service does die from time to time and I need immediate access to the Internet at some special times of day. Also, when I travel, I don't have DSL at all and the BEAM is the only way I'm going to be able to get the information I need. Thanks for responding at least to say hi and ask a couple of questions.
Blanca_O
Aug 13, 2019NETGEAR Employee Retired
Hi bgrumbin
Thank you for responding. If there is no issue with Windows 7 computers then AT&T Beam hardware is fine. Have you tried contacting AT&T as this is their device? This is for them to check software update.
Regards,
Blanca
Community Team
- bgrumbinAug 13, 2019Aspirant
Thanks for replying to my details, Bianca. Actually I started with lengthy conversations with AT&T Mobility because they were the ones who sold the device to me in the first place and are collecting the monthly fees whether I use it or not. Had a faint hope that the manufacturer of the BEAM device might have some better insight as to what is needed for it to function on a Windows 10 computer with wired mouse. Fact is, even after KILLING the mouse when I attach the BEAM, the AT&T Mobility software is unable to come up to functionality but sits "outside" on the BEAM device telling me it's "Ready to Connect" when in fact its software isn't relating to the BEAM and provides no way for me to make an actual connection to the Internet not even with the thereby primatized touchpad which is supposed *never* to come on. I'm going to try to contact AT&T "yet again" with your guidance that this is probably the issue of *their* software perhaps even rather than the "usual suspect for all probllems" the new to me Windows 10 slopperating system.
- Blanca_OAug 14, 2019NETGEAR Employee Retired
- bgrumbinAug 14, 2019Aspirant
I was able to talk with AT&T tech support this evening. The lady who talked with me walked me through the entire process which was somewhat different from what happened the first time. Originally I just plugged the BEAM device into the second USB port and it killed my mouse instead of bringing up the AT&T AllAccess software as it does on my Windows 7 computers. This time the time sequence was different.
First thing was that I reinstalled (I had uninstalled after the original fiasco) the AT&T AllAccess software and noticed that it was a *2015* dated program. It put the expected operating screen onto my Desktop so that I had quite a bit more information on what was happening during the killing of my mouse. That software did *not* kill my mouse which continued working normally. It did however claim, without any Internet access available, that there were "no updates" available as of today. That seemed to me to be a contradiction since I "seem to recall" several updates that have been installed via the BEAM of the AT&T AllAccess software during the more than four years elapsed since its stated program date.
Next thing I did was to plug in the BEAM device via a cable so that it couldn't physically interfere with the wired mouse plugged into the adjacent USB 3.0 port. An entirely new thing occurred after I plugged in the BEAM device this time. It wanted to install some software of its own (never mentioned that last time). What it installed was a directory labelled Sierra Wireless which contained after all the hassles were over with a 2015 version of some program apparently intended to work the BEAM device. It was during *that* installation of software by the BEAM device that the mouse was KILLED. I was fiddling with it throughout the early part of that installation of majorly out of date Sierra Wireless software (was Windows 10 even more than a malicious intended obfuscation of Microsoft that long ago?). Somewhere in the midst of the BEAM originated software is when my fiddling with the mouse quit working and the mouse was KILLED. That process was also what over rode my instructions via Lenovo Vantage (the manufacturers of the computer itself with Windows 10) to absolutely disable the utterly useless and dysfunctional "touchpad".
As part of my cleanup process when everything demonstrated conclusively that the AT&T AllAccess wasn't ggoing to work and that the BEAM wasn't going to work and that my mouse was quite gone and that my disabling of the "touchpad" had been over ridden during the installation of the "Sierra Wireless" software, I uninstalled AT&T AllAccess, deleted the Sierra Wireless directory in its entirety, and used Lenovo Vantage to reassert my demand that the "touchpad" be disabled (it was correctly reasserted).
If in fact (as I suspect) the Sierra Wireless software sent through the BEAM device is somehow the responsibility of NetGear, I though that this detailed description of WHAT HAPPENED might be helpful towards a solution of my very much remaining problem.