rootabaga
Android Expert
Hi, folks.
Windows 10 has been running flawlessly for me (several different installations/devices) until last week when one system was trying to install update 1803 and errored out, telling me it couldn't continue until I manually remove Avira Antivir.
Considering that the particular workstation was a clean build of Win7 (no apps installed) with a free upgrade to 10 (to get the dvd player app at no charge) and that I'd never even heard of Avira Antivirus, I knew something odd was going on. I spent lots of time with my friends Google and Bing and eventually found an answer, so thought I'd share it here for those who may run into the issue or those who are searching the web for an answer.
For whatever reason there is a file in the C:\Windows\SysWOW64\drivers folder named avipbb.sys.
This file is a system driver associated with Avira Antivirus, but why it's there for untold thousands (millions?) of users who've never installed it is a mystery. It can be safely deleted, or, if you're concerned about deleting a sys file, simply rename it to something like avipbb.sys.old (that's what I did). Then the update runs as normal.
Good luck as always...
Windows 10 has been running flawlessly for me (several different installations/devices) until last week when one system was trying to install update 1803 and errored out, telling me it couldn't continue until I manually remove Avira Antivir.
Considering that the particular workstation was a clean build of Win7 (no apps installed) with a free upgrade to 10 (to get the dvd player app at no charge) and that I'd never even heard of Avira Antivirus, I knew something odd was going on. I spent lots of time with my friends Google and Bing and eventually found an answer, so thought I'd share it here for those who may run into the issue or those who are searching the web for an answer.
For whatever reason there is a file in the C:\Windows\SysWOW64\drivers folder named avipbb.sys.
This file is a system driver associated with Avira Antivirus, but why it's there for untold thousands (millions?) of users who've never installed it is a mystery. It can be safely deleted, or, if you're concerned about deleting a sys file, simply rename it to something like avipbb.sys.old (that's what I did). Then the update runs as normal.
Good luck as always...
