AS16 & Win 10 update

Win just updated yesterday (03 Nov 17) and AS16 won't run. I have uninstalled and reinstalled the latest upgrade to AS16 with the same results. I also downloaded the complete AS16 and tried with that. It will not run. Any help is appreciated.

Happy :pilot: Flyin

AD

How come Windows 10 updated yesterday? Windows Update Day is the second Tuesday in the month, US time.

 

Anyway, my Windows 10 is fully updated, and my AS16 runs fine. I would suggest you open a support ticket with HiFi Simulations.

 

Jorgen

I was having a problem with "Error creating child window" message. FSX kept crashing. I did a google search and came across a thread that was making reference to this and the Fall Creators update of windows 10. According to this thread Microsoft in their update failed to acknowledge 32 bit programs. Their next update should restore things back to normal, but that will not be for another month. https://www.avsim.com/forums/topic/522596-update-from-lm-regarding-p3d-v34-ctd-fix/. I rolled my system back and everything is working fine.

Thanks for the reply. I did submit a trouble ticket. I just thought someone here might beable to help. As to why Win 10 updated yesterday I can't say... I was in a flight to KCRG when the notification came up telling me to reboot for the update...

AD

Thanks for the reply. I did submit a trouble ticket. I just thought someone here might beable to help. As to why Win 10 updated yesterday I can't say... I was in a flight to KCRG when the notification came up telling me to reboot for the update...

AD

 

The Windows 10 Fall Creators update was staggered so some PCs didn't get it right away. Yours was probably one of them.

It is the creators update. From the HiFi forum in response to my message the Devs are aware of the problem and are working on a fix. I will let you all know what the find...

Thanks again, AD

The strange part is then that I have the Creator's Update, and haven't had any issues at all with that, and, like I said earlier, AS16 works fine.

 

Jorgen

The problem only comes with Creator's Update (1709).

But again, if the issue comes with that update, and I have that update installed, why does the issue not show on my system? So, there must be some way around the issue.

 

Jorgen

From what I have found, the issue is with the a/v program. some work and others dont, as mine doesnt (avast A/V). I disabled it for 10 mins and ran AS16 with no problems. I flew from KDEN to KSAN with a perfect flight. To my FS family thanks for aLL OF YOUR HELP... iTS ALL UP TO hIfI and AS16.

Happy :pilot: Flyin

AD

I HATE Win10! Have four computers running it. Two work fine. The other two, if I don't use them at least every two days, I have to do a hard re-start before I can do everything. Windows 10 is Microsofts worst piece of junk I've seen. ( My opinion).

Two work fine. The other two...

You're right, nothing wrong with the computers. Definitely a W10 fault :rolleyes:.

 

Wim

Nothing wrong with Win 10. I have it on 3 computers, all fully updated, nothing wrong with any of them, even if they have been shut down for over a week when I'm away.

 

Jorgen

I would have no issues with if like the older versions I got to choose what updates and when I do them... Who knows.... AD

You know, I got to think a bit this morning.

 

Common for my 3 computers is that they all have Intel processors. One is a laptop with an i3 processor and an Intel graphics chipset (4000 srs.), another laptop has an i7 mobile 6700 processor, an Intel 530 srs. plus a nVidia GTX960M graphics chipset, and my desktop here has an i7 7700 with a nVidia GTX 960 card.

 

Could the issue (mind you, there definitely IS an issue) have something to do with the combination of processors and graphics chipsets?

 

Just speculating -

 

Jorgen

My reply was meant to be ironic (see the :rolleyes: ).

 

Wim

From what I have found, the issue is with the a/v program. some work and others dont, as mine doesnt (avast A/V). I disabled it for 10 mins and ran AS16 with no problems. I flew from KDEN to KSAN with a perfect flight. To my FS family thanks for aLL OF YOUR HELP... iTS ALL UP TO hIfI and AS16.

Happy :pilot: Flyin

AD

 

By this statement it is clear that the issue may not be W10 or AS16 related - neither update your (or any other) AV product - and the W10 update is just a coincidence.

 

Have a look at the AV history and see if it is flagging any of the AS16 files (especially the .exe file) as suspect/pending action.........

 

Another option is to delete and then reinstall the AV suite using the latest setup file from the Avast website.

Further to my response in post #18, a little info regarding W10 updates, as commented y Jorgen and Loki...........

 

It should be noted that the 'Creators' update is essentially a new 'full' version of W10 and is separate from normal updates.

 

WRT the 'official' patch day. Whilst MS still stick to this release schedule there a number of settings that affect how W10 updates. If you use a 'metered' connection, and have set the Windows update options to reflect this, downloads will be spread over time so that you don't, in theory, occur costs for exceeding any download limits that may be set by your ISP contract. The updates are delivered in small 'packets' and updates are installed as and when a number has been downloaded. This does, however, mean that your rig might not be getting updated regularly, especially if you are not constantly connected to the internet, hence the 'random' restart request that amberdog1 received. To avoid random restarts you can set 'quiet' hours on the Update settings page.

 

The 'metered' setting does not appear under the Update and Security settings (where you can run a manual update) but appears under the Network and Internet settings. When the page opens you will see the network status statement and below it is a 'Change Connection Properties' link. Click on this and you will see a number of options, including the 'metered' option along with a description.

 

Something else that might impact on how updates are delivered is a setting option called 'Choose how updates are delivered' which is found under the Update and Security settings. In the Windows Update page, under the Update Settings section is an 'Advanced Options' link. Click on this and on the new page click on the 'Choose how updates are delivered' link. The options displayed are, IMO, aimed at (and more suited to) enhancing how updates are processed on an internal network within companies etc. However, one of the options, the 'PCs on my local network and PCs on the internet' MAY help you get the updates quicker but, again IMO, can also hinder the process and, if selected, can have a detrimental impact both on your network bandwidth speeds and data usage. Change the settings according to your personal requirements.

The issue was related to my A/V, Avast (also AVG seems to have this same problem).

here is my copy from the tech at HiFi.

 

 

Please see article below for solutions as we have identified this problem with Avast and AVG:

 

http://hifisupport.kayako.com/Knowledgebase/Article/View/47/12/asp4-or-as16-fails-to-start

 

 

 

 

-

Damian Clark

HiFi Support

 

Thanks again for all of your input.

Happy :pilot: Flyin

AD

I had an issue with AS16 and AVG some time ago, very much like this one, but it was resolved by AVG and I haven't seen it since.

 

Jorgen

Jorgen do you remember what the fix was?

I remember a similar thing with ASN. Dunno if that applies here.

The fix with ASN was to put the weather engine in the virus scanner's exeption list IIRC.

 

Wim

I remember that I opened a support ticket with HiFi and they fixed things with AVG.

 

Jorgen