If you are referring to AVG, they have resolved that particular issue.
Window-Eyes Product Support Ai Squared 725 Airport North Office Park Fort Wayne, IN 46825 (802) 362-3612 www.aisquared.com -----Original Message----- From: Talk [mailto:talk-bounces+cgrabowski=aisquared....@lists.window-eyes.com] On Behalf Of Kevin Huber via Talk Sent: Monday, January 4, 2016 1:04 PM To: Ray Campbell <ray153...@gmail.com>; Window-Eyes Discussion List <talk@lists.window-eyes.com> Subject: Re: Problems with Window-Eyes 9.3.1 on both a Windows 8.1 and Windows 10 machine Hi Ray: I think that all your problems with the Windows 8.1 system and Window-eyes 9.3.1 stem from the fact that that file was flagged by your Antivirus software, and it sounds like that file that was flagged is one which is essential for Window-eyes to run properly. I had a problem like that when I first installed Window-eyes 9 on my system. The file that was flagged was one of the components that was necessary for running scripts, so I was a bit lucky I suppose. My solution was to install a different antivirus package, although you may not want to do that if you like the one that you are using. You might ask why I went to the bother of installing another antivirus program, instad of telling the antivirus package to ignore the file in question. The answer is that I tried that and it didn't seem to work. The antivirus package continued to flag that file, so I got rid of that package and installed a different antivirus software. Now everything works fine. Kevin Huber On 1/4/16, Ray Campbell via Talk <talk@lists.window-eyes.com> wrote: > Hi All: > > I'm glad to be back on the Talk list. Following is a copy of an email > I sent to WE Support documenting some major issues we're having with > Window-Eyes 9.3.1 on both a Windows 8.1 and Windows 10 machine. Just > sharing in case anyone else is having any of these issues and may, > along with the support team, have ideas on how to resolve them. At > this point in time, we don't consider Window-Eyes 9.3.1 usable on > either machine and are using JFW. We recognize, however, not everyone > has that option. > > Ray Campbell > ray153...@gmail.com > > Running Window-Eyes on an HP Pavilion with Windows 8.1, a Virtual > Machine running on a Mac with VMware Fusion and Windows 7, and an Asus > laptop running Windows 10 > > > ---------- Forwarded message ---------- > From: Ray Campbell <ray153...@gmail.com> > Date: Sat, 2 Jan 2016 17:21:30 -0600 > Subject: Problems with Window-Eyes 9.3.1 on both a Windows 8.1 and > Windows 10 machine > To: wesupp...@aisquared.com > > Hello WE Support: > > I am writing to let you know about some major issues we’re having with > Window-Eyes 9.3.1 both on our Windows 8.1 and Windows 10 machines. > Here is what is happening and what I’ve tried. > > On the Windows 8.1 machine, I ran the update from Window-Eyes 9.2 to > Window-Eyes 9.3.1 yesterday. When I got the update installed and > re-started the computer, my antivirus package, Webroot Secure > Anywhere, flagged what I believe was a Window-Eyes DLL file as a > threat. I can’t remember the entire file name, but it started with > GWHK and had the extension DLL. Webroot isn’t the most accessible > tool, but I was able to get over to where it said de-select, click it > and then hit continue. > > The problems didn’t end there. When I go to my desktop, I hear > Window-Eyes say ‘No Selected Item’. When I arrow around on the > desktop, I don’t hear anything. > > When I went into my documents folder, I noticed that using the up and > down arrow I wasn’t hearing my files and folders being read. This was > also true when I went to the folder view on my external hard drive, as > well as when I typed in a search for something from the start menu and > hit enter and the search results came up. > > Thinking there might have been something wrong with the update, and, > since I have a full 9.3.1 install because we got my wife a new Windows > 10 computer, I uninstalled Window-Eyes and used the 9.3.1 full install > to re-install the software. The problems I had didn’t go away. I > notice if I, say, go into the documents folder, then shut down and > re-start Window-Eyes, I can then read down through the list of files > and folders. But, If I go into a folder, I have the same problem > where I can’t read the list of files or folders using the arrow key > and have to shut down and re-start Window-Eyes again. > > I noticed something when I initially go into folders like documents. > When I do that, then do ctrl+backslash to open the Window-Eyes control > panel, the file announced is default.set. When I re-start > Window-Eyes, then, go into the WE control panel, I hear wineyes.set > announced. I’m thinking there could be issues with file associations > that I’m seeing. How can I fix this? > > Now, for the issues I’m seeing on my wife’s new Windows 10 laptop. > Basically, they are the same. However, I’m also seeing a situation > there in Internet Explorer. If I go to a website, then try pressing > say the ‘H’ key to navigate by headings, nothing happens. Going to > the WE Control panel I hear ‘default.set’ announced. I tried opening > ie.set and this didn’t change the situation. I used the flu 9.3.1 > install to load Window-Eyes onto the Windows 10 machine. When I > re-started the computer after doing this, Webroot didn’t flag the same > DLL as a threat. > > Can you help us resolve these issues? I did manage to look at some of > the Windows 10 information in the knowledge base and didn’t find that > there was anything readily apparent I would need to do. If there’s > something with the computer that I may have to have visually checked, > can you tell me what I should have someone look for? I have a tech > support plan for three devices from Geek Squad so they can help me. > Or, can we set up a time for me to remotely connect with you so you > can look and see what might be going on on each computer? I can make > arrangements to be here during the day to do this. > > Thanks, looking forward to hearing from you. > > > Ray Campbell > Email: ray153...@gmail.com > > Running Window-Eyes 9.3.1 both on an HP Pavilion running Windows 8.1 > and an Asus laptop running Windows 10. Both machines have Webroot > Secure Anywhere for virus protection. > _______________________________________________ > Any views or opinions presented in this email are solely those of the author > and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/huber.kevin7%40gmail.com. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/cgrabowski%40aisquared.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
