Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: glnz on March 15, 2017, 11:07:59 PM
-
For some weird reason, in XP Mode (on Win 7 Pro), I cannot install Avast Free new version 17. The Avast on-line download program cannot connect to Avast's servers. However, in XP Mode, I can connect to the outside world with everything else, including browsers in XP Mode and other updates.
I've tried a lot of different stuff, including adding the Avast on-line download exe file to the Windows Firewall in XP Mode. No luck.
Here's the resulting Avast log - in the bottom half, you'll see lots of "Next Tries". What is blocking the connection between my XP Mode and the Avast servers???
2017-03-15 21:56:20Infoinstcont[3792,3796]--
2017-03-15 21:56:20Infoinstcont[3792,3796]2017/03/15 21:56:20 START: Avast installer/updater
2017-03-15 21:56:21Infoinstup[3792,3796]Command: '"C:\DOCUME~1\XPMUser\LOCALS~1\Temp\_av_iup.tm~a03620\instup.exe" /cookie:mmm_ava_ppc_999_a1c_m /edition:1 /ga_clientid:8c2de1e5-068d-4eb6-9204-7ff6270bae3f /guid:e1c50033-7e25-496a-8f93-7a932ff02c0e /prod:ais /sfx:lite /sfxstorage:C:\DOCUME~1\XPMUser\LOCALS~1\Temp\_av_iup.tm~a03620'
2017-03-15 21:56:21Infoinstup[3792,3796]CPU: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz,1
2017-03-15 21:56:21Infoinstup[3792,3796]OS: Windows XP SP3 x86
2017-03-15 21:56:21Infoinstup[3792,3796]Memory: 11% load. Phys:3032032/3419632K free, Page:3786784/4040452K free, Virt:2037216/2097024K free
2017-03-15 21:56:21Infoinstup[3792,3796]DISKs: C:\ - 113GB free / 126GB total
2017-03-15 21:56:21Infoinstup[3792,3796]Running module version: instup.exe - '17.2.3419.0'
2017-03-15 21:56:21Infoinstup[3792,3796]Running module version: Instup.dll - '17.2.3419.0'
2017-03-15 21:56:21Infoinstupmutex[3792,3796]The ownership of the fallback mutex has been successfully taken.
2017-03-15 21:56:22Infoguiwizard[3792,3796]Running module version: HTMLayout.dll - '3.3.2.1'
2017-03-15 21:56:22Infoguiwizard[3792,3796]Loaded module version: C:\DOCUME~1\XPMUser\LOCALS~1\Temp\_av_iup.tm~a03620\HTMLayout.dll - '3.3.2.1'
2017-03-15 21:56:22Infoguiwizard[3792,3796]Setup gui was successfully started.
2017-03-15 21:56:22Infoinstupcore[3792,3796]Sfx setup update has started.
2017-03-15 21:56:22Infoservers[3792,3796]Server definition(s) loaded for 'C:\DOCUME~1\XPMUser\LOCALS~1\Temp\_av_iup.tm~a03620\servers.def': 29 (maintenance:0)
2017-03-15 21:56:22Infoservers[3792,3796]ChooseServer: selected server 'Download v6834318 AVAST9 Server' with current url 'http://v6834318.iavs9x.u.avast.com/iavs9x (http://v6834318.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:56:37Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://v6834318.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://v6834318.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 1
2017-03-15 21:56:37Infoservers[3792,3796]ChooseServer: selected server 'Download h0637628 AVAST9 Server' with current url 'http://h0637628.iavs9x.u.avast.com/iavs9x (http://h0637628.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:56:54Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://h0637628.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://h0637628.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 2
2017-03-15 21:56:54Infoservers[3792,3796]ChooseServer: selected server 'Download p3713387 AVAST9 Server' with current url 'http://p3713387.iavs9x.u.avast.com/iavs9x (http://p3713387.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:57:11Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://p3713387.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://p3713387.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 3
2017-03-15 21:57:11Infoservers[3792,3796]ChooseServer: selected server 'Download g0511470 AVAST9 Server' with current url 'http://g0511470.iavs9x.u.avast.com/iavs9x (http://g0511470.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:57:28Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://g0511470.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://g0511470.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 4
2017-03-15 21:57:28Infoservers[3792,3796]ChooseServer: selected server 'Download f5136535 AVAST9 Server' with current url 'http://f5136535.iavs9x.u.avast.com/iavs9x (http://f5136535.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:57:45Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://f5136535.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://f5136535.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 5
2017-03-15 21:57:45Infoservers[3792,3796]ChooseServer: selected server 'Download g0511470 AVAST9 Server' with current url 'http://g0511470.iavs9x.u.avast.com/iavs9x (http://g0511470.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:58:02Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://g0511470.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://g0511470.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 6
2017-03-15 21:58:02Infoservers[3792,3796]ChooseServer: selected server 'Download t5730298 AVAST9 Server' with current url 'http://t5730298.iavs9x.u.avast.com/iavs9x (http://t5730298.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:58:19Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://t5730298.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://t5730298.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 7
2017-03-15 21:58:19Infoservers[3792,3796]ChooseServer: selected server 'Download d0211227 AVAST9 Server' with current url 'http://d0211227.iavs9x.u.avast.com/iavs9x (http://d0211227.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:58:36Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://d0211227.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://d0211227.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 8
2017-03-15 21:58:36Infoservers[3792,3796]ChooseServer: selected server 'Download v6834318 AVAST9 Server' with current url 'http://v6834318.iavs9x.u.avast.com/iavs9x (http://v6834318.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:58:53Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://v6834318.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://v6834318.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 9
2017-03-15 21:58:53Infoservers[3792,3796]ChooseServer: selected server 'Download f6761140 AVAST9 Server' with current url 'http://f6761140.iavs9x.u.avast.com/iavs9x (http://f6761140.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:59:10Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://f6761140.iavs9x.u.avast.com/iavs9x/servers.def.vpx (http://f6761140.iavs9x.u.avast.com/iavs9x/servers.def.vpx)'. Next try: 10
2017-03-15 21:59:10Infoservers[3792,3796]ChooseServer: selected server 'Download s7284151 AVAST9 Server' with current url 'http://s7284151.iavs9x.u.avast.com/iavs9x (http://s7284151.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:59:12Infoservers[3792,3796]ChooseServer: selected server 'Download x6055396 AVAST9 Server' with current url 'http://x6055396.iavs9x.u.avast.com/iavs9x (http://x6055396.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:59:27Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://x6055396.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://x6055396.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 1
2017-03-15 21:59:27Infoservers[3792,3796]ChooseServer: selected server 'Download s7284151 AVAST9 Server' with current url 'http://s7284151.iavs9x.u.avast.com/iavs9x (http://s7284151.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 21:59:44Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://s7284151.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://s7284151.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 2
2017-03-15 21:59:44Infoservers[3792,3796]ChooseServer: selected server 'Download x6055396 AVAST9 Server' with current url 'http://x6055396.iavs9x.u.avast.com/iavs9x (http://x6055396.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:00:01Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://x6055396.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://x6055396.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 3
2017-03-15 22:00:01Infoservers[3792,3796]ChooseServer: selected server 'Download t5730298 AVAST9 Server' with current url 'http://t5730298.iavs9x.u.avast.com/iavs9x (http://t5730298.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:00:18Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://t5730298.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://t5730298.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 4
2017-03-15 22:00:18Infoservers[3792,3796]ChooseServer: selected server 'Download f7031642 AVAST9 Server' with current url 'http://f7031642.iavs9x.u.avast.com/iavs9x (http://f7031642.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:00:35Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://f7031642.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://f7031642.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 5
2017-03-15 22:00:35Infoservers[3792,3796]ChooseServer: selected server 'Download h1874089 AVAST9 Server' with current url 'http://h1874089.iavs9x.u.avast.com/iavs9x (http://h1874089.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:00:52Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://h1874089.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://h1874089.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 6
2017-03-15 22:00:52Infoservers[3792,3796]ChooseServer: selected server 'Download g0511470 AVAST9 Server' with current url 'http://g0511470.iavs9x.u.avast.com/iavs9x (http://g0511470.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:01:09Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://g0511470.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://g0511470.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 7
2017-03-15 22:01:09Infoservers[3792,3796]ChooseServer: selected server 'Download l5978727 AVAST9 Server' with current url 'http://l5978727.iavs9x.u.avast.com/iavs9x (http://l5978727.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:01:26Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://l5978727.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://l5978727.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 8
2017-03-15 22:01:26Infoservers[3792,3796]ChooseServer: selected server 'Download z2217299 AVAST9 Server' with current url 'http://z2217299.iavs9x.u.avast.com/iavs9x (http://z2217299.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:01:43Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://z2217299.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://z2217299.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 9
2017-03-15 22:01:43Infoservers[3792,3796]ChooseServer: selected server 'Download v4618535 AVAST9 Server' with current url 'http://v4618535.iavs9x.u.avast.com/iavs9x (http://v4618535.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:02:00Errordldwrap[3792,3796]HttpGet: An error 41227 (0x0000A10B) [Downloader system error] has occured when downloading a file from 'http://v4618535.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx (http://v4618535.iavs9x.u.avast.com/iavs9x/prod-pgm.vpx)'. Next try: 10
2017-03-15 22:02:00Infoservers[3792,3796]ChooseServer: selected server 'Download f5136535 AVAST9 Server' with current url 'http://f5136535.iavs9x.u.avast.com/iavs9x (http://f5136535.iavs9x.u.avast.com/iavs9x)' of type 'URL_TYPE_DOWNLOAD_PROGRAM'.
2017-03-15 22:02:02Errorpkgengine[3792,3796]LoadLatestProdAndParts: download product file 'prod-pgm.vpx' has failed. Status: 41227 (0x0000A10B) [Downloader system error]
-
Not that I have any experience of setting up a VM and installing or installing XP in it and then installing avast in that OS.
But, I would have thought that it would be wise to download the full off-line installer and not the on-line stub-installer that has to pull down the relevant components from the internet.
-
DavidR - I tried that too, but then the 2-27-17 offline install could NOT connect to the Avast servers to do updates. It would just get stuck.
I completely UNinstalled that one using Avast Clear in Safe Mode in XP Mode. Then tried the online installer again. No luck.
And I can see I'm not the only one. See https://forum.avast.com/index.php?topic=197947.0 (https://forum.avast.com/index.php?topic=197947.0) This is a real, new problem.
-
What is your firewall ?
Also have you given permissions to the avast executables, avastui.exe, instup.exe, ashUpd.exe and avastsvc.exe if your firewall has outbound checking.
Presumably you had this up and running before ?
-
Its almost certainly due to the well known AVAST virtualization conflict.
Turn off AVAST virtualization and it should be possible to install it.
I'd ask why you want to install AVAST twice, assuming you're using it on the host machine. You should be avoiding using XP online except for anything other than the essentials ie. updating the software you have installed which needs to use used with XP.
I'd suggest you use something lighter and less intrusive and you'll find that with even 'just' 1GB of assigned XP VM RAM its plenty fast enough for most purposes.
-
David R - In XP Mode, I added numerous Avast exe's to the Windows XP Firewall - did not help at all.
In the "host" Win 7 Pro 64-bit firewall, I was lost - it is controlled quite differently, and I did not see any way to do anything similar. However, I saw that Microsoft Windows Virtual PC already has permissions to connect to the internet.
Reminder that, in XP Mode, my other programs can connect to the outer web without a problem - browsers, Malwarebytes update, Windows updates, etc. There is no firewall issue, and they are NOT specifically permitted in either forewall.
So I don't think the firewalls are at fault. See also the other thread to which I give a link above.
Cluster-Lizard - In BOTH the Win 7 Pro "host" and in the XP Mode, I UNchecked Enable Hardware Assisted Virtualization. In fact, I did that FIRST. No help. (By the way, you can't even start XP Mode until you UNcheck Enable Hardware Assisted Virtualization in the Win 7 Pro host.)
David R and Cluster - your suggestions certainly make sense, but I already did both. They are not the cause of the problem. Something else is interfering.
-
I'm sorry the suggestions haven't worked or you had already applied them. I'm at a loss as to what else to suggest given I'm a novice in the land of setting up a VM OS and how it might interact (or not) with avast and the Host.
-
I am using exactly the same Windows OS (Win7 Pro 64Bit) with XP Mode and I assumed at the time I set it up about 6 months ago now all the trouble I had with trying to install AVAST in XP Mode was entirely due to the virtualization issue. But there is a possiblity it was the VM software too because I initially tried using MS Virtual PC then Oracle.
I couldn't get them to work so I used a restore point and then tried Virtual Machine. It was then at some point during this process I learned about the virtualization problem. I disabled it in AVAST and made sure my BIOS Intel Assisted Virtualization was enabled (it was by default).
After all that the VM started working and as I now 'knew' the problems were being caused by the use of AVAST virtualization I thought it prudent not even to risk messing up the VM by trying to install it under XP Mode.
As I understand in AVAST installs with the virtualization feature on by default. Isn't this still the problem here?
You've turned it off on the host machine but the XP Mode AVAST install is a separate system. Its a chicken and egg thing, you can't turn it off in the virtualized XP Mode because you need to install it first to be able to do that. Unless there is an AVAST install menu option to turn it off (is there?) it won't install because of the virtualization conflict.
-
C-L -- Thanks again for your thoughts.
In my struggles the last few days, I did install Avast Free 17 in my XP Mode by getting the full, off-line install program (250MB ±) into my XP Mode Downloads folder. After it started running, I turned OFF its Enable hardware-assisted virtualization (EHAV) in Troubleshooting. However, it would still NOT connect to Avast's servers to do any updating of the definitions - it stuck at Feb 27, 2017.
The lack of connection to Avast's servers is the same as when I try to re-install Avast Free 17 using the on-line installation stub (600 KB ? - don't remember).
There's something about being in XP Mode that the new Avast Free 17 and the Avast servers don't like. It's very weird.
Again, at least one other user is having this problem - see https://forum.avast.com/index.php?topic=197947.0 (https://forum.avast.com/index.php?topic=197947.0) . And my other programs in XP Mode connect to the internet, update and do everything else without complaining. For example, my Malwarebytes Free in XP Mode updates itself without a problem. And yesterday I got more updates to XP itself. (I'm using the POS hack to continue to get updates for XP.)
So, anyway, EHAV in Troubleshooting isn't the problem.
-
I don't know why you would need to run avast in XP Mode in a VM of XP, essentially it shouldn't be any different from running 1.7.2.2288 in XP normally.
This system is XP Pro SP3 and the latest avast free version and I haven't had to set avast to run in XP mode as it is on an XP System.
I don't see why that would be any different when running it on a VM, it isn't like you are running it in the win7 host, you are running it under XP, but in a VM environment. I actually have a program that I need to run in compatibility mode (for win 98).
Unless this is confusion and you actually you are running avast in an XP VM, you aren't actually setting the avast program to run in XP (compatibility) mode.
-
David R - You are missing the point. Please re-read my posts here.
XP Mode in Windows Virtual PC on a Win 7 Pro host is a real, functioning computer. It connects to the world, and it can run programs that also connect to the world. Now, when I start it up, it warns me with a red shield and a balloon that I don't have any AV installed.
Avast AV Free version 17 does not install in XP Mode. That's an Avast problem. See the other thread here (by nedo ?) for proof that I'm not the only one with this issue. Avast AV Free version 12 had been running in XP Mode just fine. Version 17 is wrong somehow.
By the way, I have a completely different XP computer, in which Avast AV Free version 17 is running well. Avast's servers don't like XP Mode.
-
I honestly don't know what 'you' mean by XP Mode.
For me there is XP Compatibility Mode, to run an old program that couldn't run on the installed OS, such as that in my attached image running a program in win98 compatibility mode on my XP OS.
This completely different to running a Virtual Machine that has XP installed on it with a different Host OS.
-
I ask myself why to connect XP Mode to the internet.
My main computer is a Win7 system; for some old applications I need XP and run XP under VMware. But I never go online with that. I don't need malware shields there because all files accessible in XP come from Win7 which is shielded.
-
stibi - on those rare occasions I want to run XP Mode, I want it to be able to access the internet like any other computer. And it is NOT "shielded" by the AV on its Win 7 Pro host.
Avast AV Free 12 worked just fine in XP Mode. Avast AV Free 17 does not work in XP Mode. That's called a "flaw"; it's not a "feature".
David R - This thread has nothing to do with Compatibility Mode. Let's stay on topic, please.
-
I simply don't know what you mean by XP Mode as I mentioned in my last post.
Having been an XP Pro user for many years, isn't something that I recognise at all.
-
You jest? If not shame on you! :)
Google for heaven's sake.
https://www.microsoft.com/en-us/download/details.aspx?id=8002
XP Mode is a free from MS optional download (<500MB) allowed with certain versions of Win7 like Pro to install a near enough full WinXP 32Bit OS on a virtual machine. You have the choice of what virtual machine software to use.
As an effectively separate OS it should have separate anti-virus/anti-malware protection particularly if used online.
IMHO installing AVAST or any other full AV suite is overkill and will just slow down the VM. As long as you're not using it for casual browsing and risky downloading a lighter weight alternative which doesn't have any issues when running on a VM installed Windows OS should be OK. At least that is the information I gleaned from my researches before installing it.
The VM is just a program which runs on the host machine so AVAST will include it and any shared drives/volumes during a Full System Scan. As long as you do that regularly I would have thought that made it a pretty safe set up. Isn't scanning from outside an OS, usually via disc or USB, one of the primary techniques used for finding and dealing with malware anyway?
-
Thanks to Mr. Bone in another thread - I have successfully downloaded and installed Avast AV Free 12 in my XP Mode, was able to update definitions ONLY, and it's now running a boot-time scan.
Proof positive that Avast 17 is faulty.
Many thanks to all for suggestions !!! Avast 17 still needs to be fixed.
-
@ Cluster-Lizard2014
Never ever heard of it; you would have had to have had some need of it before you ever went looking for it, but then if don't even know you need it you are hardly going to know of it.
A bit like the chicken and the egg which came first, the knowledge or the need.
I have had XP Pro for many, many years a legit retail license and disk so I have never needed it even if I knew about it.
-
David R - One of the reasons I use XP Mode is to test the ongoing updates of XP using the POS hack before I inflict those updates on my real XP machine.
Anyway, XP Mode was a hugely promoted feature of Win 7 when 7 first came out. And it's my personal introduction to virtual computing.
You should try it - it's fun. (But first you have to turn off Enable hardware-assisted virtualization in Avast - Troubleshooting.)
-
Glad to read the glnz problem has been resolved.
It would help if there was a link to the thread with the solution mentioned.
XP Mode: There is hardware and software that even with Win7's good backwards compatibility that will only run under XP and XP Mode on a VM is the easiest way of doing this.
Having said that I've still found stuff, mostly games, that despite being made for use with XP for some reason don't like XP Mode and need to be run on a full XP installation. I've even found others for earlier Windows OS like Win98 that won't work using XP Mode even using Win98 the compatibility option but will run pretty well using Win7 Pro 64Bit with nothing more than the resolution fixed to 640x480.
In short XP Mode gives you more options but it certainly is not a guaranteed solution for all legacy hardware/software. Of course like anything else it pointless installing unless you do have a specific need for it.
-
C-L - The "glnz problem" will never be resolved.
-
David R - One of the reasons I use XP Mode is to test the ongoing updates of XP using the POS hack before I inflict those updates on my real XP machine.
Anyway, XP Mode was a hugely promoted feature of Win 7 when 7 first came out. And it's my personal introduction to virtual computing.
You should try it - it's fun. (But first you have to turn off Enable hardware-assisted virtualization in Avast - Troubleshooting.)
I avoided win7 for some considerable time, so I wasn't subjected to the feature/hype, I only got win7 (a little over 3 years ago) when I bought a netbook as a backup system and that was already on SP1 by then. My netbook wouldn't pull the skin of a rice pudding so I wouldn't even try setting up XP Mode.
Acer Aspire One, Win7 Starter (32bit) SP1, 10.1", 1024X600 screen, 2GB DDR3 RAM, Intel Atom N255 (1.5GHz dual core) CPU and 250GB HDD.
-
I tried installing Avast 17 in XP Mode today and the installation failed several times. Then, when I shut down and restarted XP Mode, it had to recover from a serious error. So the attempted Avast 17 installation rendered serious damage to my XP Mode.
I am giving up on Avast 17 for XP Mode. I will download and run MS Security Essentials and then keep XP Mode disconnected from the internet.
I use XP Mode only for an application which is not internet dependent. I don't think there is ever a need to use the internet with XP Mode. It has SP3 and as far as I can tell is fully updated as of the end of XP support.
-
Infti - thanks for your post.
So Avast STILL needs to be fixed !! Incredible.
Avast is spending lots of money and attention on marketing and NOT fixing these issues.
Infti - by the way, you can continue to get updates for XP by doing the POS hack. Google it. MSFN has the best thread on this by far. I'm up to date as of this morning (which was a time zone change in southern Chile - was very funny.)
-
glnz,
so you are able to install avast in the XP vm, right ?
No clue if it will make a difference as I can't test it.
(Don't have W7 system at the moment.)
But does it makes a difference if you disable HW VM in the bios/uefi ?
-
Eddy - why would I disable hardware virtualization in BIOS/UEFI if I want to use it? Why should I disable a feature of my PC because Avast isn't set up right?
Not only that, but if you read up a bit, you'll see that I'm leaving ON Avast's "Enable hardware-assisted virtualization" when I'm not using XP Mode.
What's your point?
-
Because it sometimes is causing problems.
-
Eddy - you mean "Because Avast sometimes is causing problems".
And to clarify - Avast 17 does not work in a virtualized OS. 12 does. But 17 doesn't. So 17 is broken.
-
Some unpleasant posts here.
People are trying to help - no need to be unkind.
If someone doesn't know something - politely explain.
No need for tactless words - makes unpleasant reading for others.
Treat others the way you would like to be treated yourself.
-
Alicia - you may have a point.
But Avast is not staying on top of tech complications.
Another thread explains how Avast 17 hogs the hardware-assisted virtualization on many PCs, when this problem was fixed before and was not happening in 12.
This thread explains how Avast 17 does not work INSIDE a virtualized OS but 12 does.
The big story here is not whether I use a nasty tone in these comments, but whether Avast is falling behind the curve.
If Avast can't handle virtualization outside or inside, how can we be confident that it is doing its job and protecting us from malware?
-
glnz
It wasn't your comments that I was referring to....
I've had problems too* and know how frustrating it can be.
*Don't want to speak too soon, but despite what I originally thought it seems a clean installation of Avast may have solved them (extended start-up time / behaviour shield intermittently failing).
Hope yours gets resolved.
-
*Don't want to speak too soon, but despite what I originally thought it seems a clean installation of Avast may have solved them (extended start-up time / behaviour shield intermittently failing).
I've still had a few instances of Behaviour Shield being disabled on system restart. The one thing that I haven't done is a clean reinstall. I had thought that I had it cured. I've noticed that Behaviour Shield is set to Manual for startup in Windows. How long has it been since you did a clean install? How many cold restarts of Windows?
-
Have you - with XP SP3?
I asked in another topic I opened:
Would you kindly tell me if I should uninstall Avast through Add / Remove Programs or use Avast Uninstall Utility for a clean installation?
Eddy: "Do both and use the off-line installer of the latest avast version to install again."
I did that on 18th April.
6 cold restarts of Windows, no Behaviour Shield failure yet aside from directly after reinstallation - "All shields are on" - "Your system is secured", no errors in Event Viewer. Before the clean installation with Avast rootkit scan at start-up checked it took 25 minutes for the full on hard drive activity light to drop at start-up - I couldn't use my computer during that time! Now it takes around 6 minutes. Such a relief, no more hanging around.
"I've noticed that Behaviour Shield is set to Manual for startup in Windows."
Yes, I previously noticed that too and asked whether I should set it to automatic. I haven't altered that manual setting.
-
Alicia and Gopher - Please start a new thread about the Behavior Shield issue.
Perfectly valid issue, but this thread is about Avast 17 not working in XP Mode.
Thanks.
-
I already did - someone asked me a question here - I answered it once.
Rude.
-
I already did - someone asked me a question here - I answered it once.
Rude.
Alicia, thanks for your answer.
-
@David - just for information:
I use Win7 with my Desktop & Win10 with the Notebook.
In both cases I need some old programs based on 32-bit Windows and also an old but much used own database tool with MS-Dos. They run only with XP, and so I use them with the help of XP-Mode under a virtual machine (VM-ware Player).
In my case I don't need internet services inside the VM; so don't need an extra virus program. Avast running on the host is enough to be safe.
-
@glnz
Hi!
Maybe it's just the 'XP Mode', which is confusing somebody, I don't know exactly. Sorry.
BTW: Did you ever try to have 2 systems on one machine using 2 HD (see first line of my sig)?
=Snake=
-
snake - My Dell Optiplex 7010 with Win 7 Pro 64-bit (and XP Mode) is actually a dual-boot machine that also has Win 10 Pro 64-bit. XP Mode is only in the Win 7, and I have Avast only in the Win 7 (version 17) and in its XP Mode (version 12 because 17 does not work inside XP Mode).
That Dell Optiplex 7010 has 16GB RAM.
With Avast's recent problems - and because it is now so so bloated - I never installed Avast in the Win 10, and the Win 10 runs only Windows Defender. That has been totally issue-free.
I also have Malwarebytes Free on both sides (and in the XP Mode) and run it manually from time to time (and also to vet downloaded items).
I also run SpywareBlaster Free and, in some other PCs for the family, Spybot S&D's "Immunization".
-
1. My Dell Optiplex 7010 with Win 7 Pro 64-bit (and XP Mode) is actually a dual-boot machine that also has Win 10 Pro 64-bit.
2. XP Mode is only in the Win 7, and I have Avast only in the Win 7 (version 17) and in its XP Mode (version 12 because 17 does not work inside XP Mode).
3. I also run SpywareBlaster Free and, in some other PCs for the family, Spybot S&D's "Immunization".
1: If you are correct, you have a triple-boot machine! The prob seem to be XP Mode under W7!
2: You have different Avast versions in W7 and inside XP Mode!
What I did: install of XP on first HD with Avast version 12 and another install of W7 on 2nd
HD with Avast version 17!!! NO probs at all!
3: I think both wan't harmonize with Avast. So I would delete them.
=Snake=
-
Snake - yes - the problem is only in XP Mode in Win 7 Pro. Sorry, but that is the only issue in this thread.
I am using only one HD for the dual-booting. It has numerous partitions. Suggestion: iReboot is a very useful tool for dual-booting.
I use a different HD for data files.
I might install a third HD for backups.
-
1. I am using only one HD for the dual-booting. It has numerous partitions. Suggestion: iReboot is a very useful tool for dual-booting.
2. I might install a third HD for backups.
1: Ok, I see. Dual-booting works with 'Boot-manager' (MS), too.
2: You should think it over: what, if you can't boot anymore? Try external HD!
=Snake=
-
So it is almost the end of August 2017 and this still does not work. I do realise that there are a limited number of Avast users that would like it to work under XP mode but the only alternative at the moment is Panda.
Windows 7 Pro(Avast working perfectly) but XP mode is still failing.
Installation by the online installer fails to download packages.
Offline installer works, but updates fail.
ping files.avast.com under Win7 works, under XP mode times out. (XP mode ping works fine to other sites). Changing ISP has no effect. Changing DNS to Google's 8.8.8.8 or 4.4.4.4 has no effect.
Curiously, the ping to files.avast.com under Linux on the same networks has a long initial pause and then springs to life.
Is there anyone at Avast who can shed a little light on this?
-
So it is almost the end of August 2017 and this still does not work. I do realise that there are a limited number of Avast users that would like it to work under XP mode but the only alternative at the moment is Panda.
Windows 7 Pro(Avast working perfectly) but XP mode is still failing.
Installation by the online installer fails to download packages.
Offline installer works, but updates fail.
ping files.avast.com under Win7 works, under XP mode times out. (XP mode ping works fine to other sites). Changing ISP has no effect. Changing DNS to Google's 8.8.8.8 or 4.4.4.4 has no effect.
Curiously, the ping to files.avast.com under Linux on the same networks has a long initial pause and then springs to life.
Is there anyone at Avast who can shed a little light on this?
Reported to Avast. Be patient, it's the weekend. :)
-
Based on stats we don't see any drop in Win XP installs. It looks like isolated issue on your PC. Isn't it possible that the PC is infected and malware is blocking files.avast.com? We saw such cases in past.