Confirmed it was MSE that was causing my freeze issues, I confirmed it in another way. When I exit FSX I always click on the red X in the top right corner of the window (I always use windowed mode) after clicking that if you haven't changed one of the default settings you should get a pop up message asking you if you are sure you want to exit the sim. That pop up message was taking the exact same amount of time to appear (actually nearly 10 seconds not 5 as I said earlier) as the freezes were long in FS itself. After excluding the drive from being scanned in Microsoft Security Essentials the exit confirmation message and autosaves now take less than a 10th of a second to appear/complete exactly like things used to be in the past for me. Mystery solved for me.

Because of stuttering and CTD's I used to get when I bought FS9, I've always turned off my AV (currently Kaspersky) before running FSX by running a batch file before launching. The following commands stop the Kaspersky service and processes.

@echo off

net stop "Kaspersky Anti-virus 6.0"

pskill -t avp.exe(pskill is a free ms resource kit tool) To find out what services are running, open 'services.msc' from a command line/window, the service name is the one in the left column. To stop a service from a command line, just type: net stop "service name" - AV products usually have an option to protect services from being manually stopped, you will have to disable this option. To find out what processes are running, type 'tasklist' in a command window.

Better yet don't install trash like Kaspersky or McAfee in the first place MSE up until very recently used to be very good at not interfering with FSX even with no excludes set for FSX specifically. I have a feeling something in this Flexnet licencing system that PMDG uses to protect the NGX may be behind the cause of the long freezes, the exclude in MSE for FSX has stopped the problem for me. This is all conjecture though about Flex-whatever its called..

"the exclude in MSE for FSX has stopped the problem for me" Andy, I'm running MSE and I'll be glad to know what you did exclude exactly in MSE, the whole FSX folder ? or something else in that folder ? Many thanks

I actually did the whole drive as it only really has FSX related stuff on their, but I think excluding all the FSX path should be enough. I'll change it to that on my system too and see how I go. EDIT: Yes just excluding everything from ...\Microsoft Games\ does work OK for me still.

Hello all, I dont know if this reply is relevant or not but here goes. I have not applied any of the fixes to the 737ngx but initially I did get panels freezing during the cockpit setup and the reply from Support was to reduce the sliders in FS scenery etc., which I did. On opening FSX splash screen I selected from change aircraft the 737 I wanted then selected desired airport and time of season then Fly Now. I then let the aircraft initialise, selected commands in FSUIPC and finally Pressed F9. From that time I have had no problems whatsoever flying this aircraft it has behaved impeccably just as one would expect. I am not suggesting this procedure I have adopted is a FIX but if it works for me it might work for others. I am very hesitant to apply the SP1 when it becomes available unless someone can persuade me otherwise. richard welsh.

FSUIPC4 Autosave enabled + the whole FSX folder excluded from MSE scanning ------>> the micro-freezes seem to have vanished !! (to be confirmed on the long term) + FSUIPC Autosave feature seems to be working fine at last ! (to be also confirmed) Thanks very much Andy for providing the "trick" we were all missing

That's great news Jean-Louis, thanks for the feedback.