1. Fsuipc Download

I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again! It is crippled - it won't run P3D because I had to substitute an older non-DX11 video card. But it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch.

In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas!

Great news Pete! That is with a couple of reservations for my use.I have seen 'the 'G3D crash' patch' do it's thing several times recently when I was flying around the EU with OrbX Global + Vector + Europe LC + Hybrid mode. Also, I and others in the 91st Bombardment Group use those weather setting options in FSX during the missions that we fly because we can not tolerate 'different wind directions/speeds' betwen users and we can not dictate to our members that they buy a commercial weather engine and then be constantly 'chasing the upgrade path'! We have resorted to using weather themes, both the 'canned varity' and those that I create with the FS2004 Weather SDK.

This keeps us all in the same environment except, as I saw during todays mission', when we crossed into another 'wind layer' and 4 of the 5 of us got the correct, gradual shift but oone pilot who did not have his FSUIPC weather settings set correctly did NOT get the wind changes. So, bottom line, there are those of us who use those wind smoothing functions. That said, if they continue to work for FSX but not FSX-SE, that would not be a problem as we will never bbe flying as a group on Steam. We require the access to the Digital Theme Park servers vis the FSX 'Lan' connect option, which is missing in FSX-SE. Again, thanks for the quick work on this in spite of your 'ill' machine and the coming holidays! Paul EDIT: I just had a look at my FSX FSUIPC4 log for this mornings 6-hour flight to Berlin and back from UKBA: It caught several G3D errors!

Great news Pete! That is with a couple of reservations for my use.I have seen 'the 'G3D crash' patch' do it's thing several times recently when I was flying around the EU with OrbX Global + Vector + Europe LC + Hybrid mode. Also, I and others in the 91st Bombardment Group use those weather setting options in FSX during the missions that we fly because we can not tolerate 'different wind directions/speeds' betwen users and we can not dictate to our members that they buy a commercial weather engine and then be constantly 'chasing the upgrade path'!

We have resorted to using weather themes, both the 'canned varity' and those that I create with the FS2004 Weather SDK. This keeps us all in the same environment except, as I saw during todays mission', when we crossed into another 'wind layer' and 4 of the 5 of us got the correct, gradual shift but oone pilot who did not have his FSUIPC weather settings set correctly did NOT get the wind changes. So, bottom line, there are those of us who use those wind smoothing functions. That said, if they continue to work for FSX but not FSX-SE, that would not be a problem as we will never bbe flying as a group on Steam. We require the access to the Digital Theme Park servers vis the FSX 'Lan' connect option, which is missing in FSX-SE.

Again, thanks for the quick work on this in spite of your 'ill' machine and the coming holidays! Paul EDIT: I just had a look at my FSX FSUIPC4 log for this mornings 6-hour flight to Berlin and back from UKBA: It caught several G3D errors! I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again! It is crippled - it won't run P3D because I had to substitute an older non-DX11 video card.

But it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too.

Happy Christmas! This part of your post is confusing me. Are you talking about FSX or FSX-SE? Have you got any information whatsoever about G3D crashes in FSX-SE? I cannot apply the same patch in SE as I do in FSX because the code I patch just isn't there, or is there but is unrecognisable.

And don't forget there are many other G3D crashes which FSUIPC never patched. Pete Pete, sorry for the confusion. I am talking about FSX as that is my primary online simulator. It wasn't clear to me that those comments about wind smoothing and G3D errors were FSX-SE only conditions. As long as the wind smoothing and G3D crash protection still works in FSX I'm happy. The log file snippets I posted were from FSX and just posted to illustrate that I 'use' that function, for lack of a better term:) Paul.

Errr, but it does/did. I see you released an update for it. No offense, but I give you a bug report that definitely shows it was caused by the program (and verified by many others on forums) and that's the kind of response? I'm afraid that FSUIPC is now so complex, and old (FSUIPC4, the 4th incarnation) has now been continuously developed now for 9 years - and every update with no extra charge, mind - that an old man like myself (well over 71 now), who should have stopped years ago, doesn't remember everything all the time and sometimes makes mistakes. But I do try and make up for it. Believe me, there are plenty of bug reports here which the reporter 'definitely shows is caused by FSUIPC' which are nothing of the kind and in fact are mostly shown not to be later on. Problems which come and go with FSUIPC's presence are often much more complex than you'd think, what with the resulting different memory arrangements plus so many applications, be they inside and outside FS, using it when it is detected.

Apologies again, and do have a very Happy Christmas! Pete, You've been a strong presence in the flight simulation community since the dawn of flight simulation technologies on home computers. With your mention that you should have stopped years ago (by the way, I'm glad you haven't - yet) and your mention of your age being over 71 now, are there any future plans (or at the very least, desires) to hand off FSUIPC to a successor who'd be well qualified to continue development of it? Regards, Joshua Robertson (creator of FS Real Time) 3D Softworks Design Studios www.3dsoftworks.net.

You've been a strong presence in the flight simulation community since the dawn of flight simulation technologies on home computers. With your mention that you should have stopped years ago (by the way, I'm glad you haven't - yet) and your mention of your age being over 71 now, are there any future plans (or at the very least, desires) to hand off FSUIPC to a successor who'd be well qualified to continue development of it? Not at present. Are you volunteering?;-) I suspect I might shuck off 64-bit when that (inevitably?) comes to Prepar3D.

Any volunteer will have a hard job with my code. I gave up commenting code many years ago. Too much typing!;-) Regards Pete. Why did you post about six messages with nothing but 'Hi Peter' in them?

You are using the wrong version of FSUIPC - you need 4.738a. Pete Sorry peter about the posts i know of 1 but not 6 I hit tab by habit and all went mad. OK about 4.738a no I will not be I have redownloaded now and will reinstall to night when I get home. Do not see any update about it being an 'a' ver. Thank you for your fast reply will post this info on our user forum so other there know.

Best of the season to you.

Welcome aboard Please, observe following rules:. Read all of my instructions very carefully. Your mistakes during cleaning process may have very serious consequences, like unbootable computer. If you're stuck, or you're not sure about certain step, always ask before doing anything else. Please refrain from running any tools, fixes or applying any changes to your computer other than those I suggest. Never run more than one scan at a time.

Keep updating me regarding your computer behavior, good, or bad. The cleaning process, once started, has to be completed. Even if your computer appears to act better, it may still be infected. Once the computer is totally clean, I'll certainly let you know.

If you leave the topic without explanation in the middle of a cleaning process, you may not be eligible to receive any more help in malware removal forum. I close my topics if you have not replied in 5 days. If you need more time, simply let me know. If I closed your topic and you need it to be reopened, simply PM me.

Your computer is infected with ZeroAccess rootkit and more. Keep in mind though that seeing 32-bit processes in 64-bit Windows is normal.

Download RogueKiller from one of the following links and save it to your Desktop:. Close all the running programs.

Windows Vista/7/8 users: right click on RogueKiller.exe, click Run as Administrator. Otherwise just double-click on RogueKiller.exe.

Pre-scan will start. Let it finish. Click on SCAN button. Wait until the Status box shows Scan Finished. Click on Delete.

Wait until the Status box shows Deleting Finished. Click on Report and copy/paste the content of the Notepad into your next reply.

RKreport.txt could also be found on your desktop. If more than one log is produced post all logs. If RogueKiller has been blocked, do not hesitate to try a few times more. If really won't run, rename it to winlogon.exe (or winlogon.com) and try again Please download (MBAM) to your desktop. If you already have MBAM 2.0 installed scroll down.

Double-click mbam-setup-2.0.0.1000.exe and follow the prompts to install the program. At the end, be sure a checkmark is placed next to the following:. Launch Malwarebytes Anti-Malware. A 14 day trial of the Premium features is pre-selected.

You may deselect this if you wish, and it will not diminish the scanning and removal capabilities of the program. Click Finish. On the Dashboard, click the ' Update Now ' link. After the update completes, click the ' Scan Now ' button.

Or, on the Dashboard, click the Scan Now button. If an update is available, click the Update Now button. A Threat Scan will begin. When the scan is complete, if there have been detections, click Apply Actions to allow MBAM to clean what was detected. In most cases, a restart will be required. Wait for the prompt to restart the computer to appear, then click on Yes.

If you already have MBAM 2.0 installed:. On the Dashboard, click the ' Update Now ' link. After the update completes, click the ' Scan Now ' button. Or, on the Dashboard, click the Scan Now button. If an update is available, click the Update Now button.

A Threat Scan will begin. When the scan is complete, if there have been detections, click Apply Actions to allow MBAM to clean what was detected. In most cases, a restart will be required.

Wait for the prompt to restart the computer to appear, then click on Yes. How to get logs: (Export log to save as txt).

After the restart once you are back at your desktop, open MBAM once more. Click on the History tab Application Logs.

Double click on the Scan Log which shows the Date and time of the scan just performed. Click 'Export'. Click 'Text file (.txt)'. In the Save File dialog box which appears, click on Desktop.

In the File name: box type a name for your scan log. A message box named ' File Saved' should appear stating ' Your file has been successfully exported'.

Click Ok. Attach that saved log to your next reply. (Copy to clipboard for pasting into forum replies or tickets). After the restart once you are back at your desktop, open MBAM once more. Click on the History tab Application Logs. Double click on the Scan Log which shows the Date and time of the scan just performed.

Click ' Copy to Clipboard'. Paste the contents of the clipboard into your reply. Please download by Xplode onto your desktop.

Close all open programs and internet browsers. Double click on adwcleaner.exe to run the tool. Click on Scan button. When the scan has finished click on Clean button.

Your computer will be rebooted automatically. A text file will open after the restart. Please post the contents of that logfile with your next reply. You can find the logfile at C: AdwCleanerS1.txt as well. Please download to your desktop.

Shut down your protection software now to avoid potential conflicts. Run the tool by double-clicking it. If you are using Windows Vista, 7, or 8; instead of double-clicking, right-mouse click JRT.exe and select 'Run as Administrator'. The tool will open and start scanning your system. Please be patient as this can take a while to complete depending on your system's specifications.

On completion, a log (JRT.txt) is saved to your desktop and will automatically open. Post the contents of JRT.txt into your next message. Broni; Thank you very much for your pront response, much appreciated. Yes, I'm well aware of 32 programs running on win 64 versions. But I also have a decent grasp of which programs I'm running are 64 or 32. In particular IE. I when I installed IE 11 (time ago) I created two icons on my quick lunch bar, one for the 32 version and another for the 64 to use until most of the websites where updated.

For a ling time now I only have been using the 64bit. That is precisely what made me wonder, as I saw in task manager, that IE was running no matter the icon I used, in 32, and of course, as mentioned all the other applications. Below the sequence of logs as requested Kind regards Kano. Please download ComboFix from, or to your Desktop.Note: In the event you already have Combofix, this is a new version that I need you to download.

It is important that it is saved directly to your desktop. Never rename Combofix unless instructed.

Close any open browsers. Very Important! Temporarily disable your anti-virus and any anti-malware real-time protection before performing a scan.

They can interfere with ComboFix or remove some of its embedded files which may cause 'unpredictable results'. Click on to see a list of programs that should be disabled. The list is not all inclusive. If yours is not listed and you don't know how to disable it, please ask. Close any open browsers. WARNING: Combofix will disconnect your machine from the Internet as soon as it starts.

Please do not attempt to re-connect your machine back to the Internet until Combofix has completely finished. If there is no internet connection after running Combofix, then restart your computer to restore back your connection. If the connection is not there use restore point you created prior to running Combofix. Double click on combofix.exe & follow the prompts.

If Combofix asks you to install Recovery Console, please allow it. If Combofix asks you to update the program, always do so. When finished, it will produce a report for you. Please post the 'C: ComboFix.txt'.

Fsuipc Download

Note 1: Do not mouseclick combofix's window while it's running. That may cause it to stall. Note 2 for AVG and CA Internet Security (Total Defense Internet Security) users: ComboFix will not run until AVG/CA Internet Security is uninstalled as a protective measure against the anti-virus. This is because AVG/CA Internet Security 'falsely' detects ComboFix (or its embedded files) as a threat and may remove them resulting in the tool not working correctly which in turn can cause 'unpredictable results'. Since AVG/CA Internet Security cannot be effectively disabled before running ComboFix, the author recommends you to uninstall AVG/CA Internet Security first.

Use AppRemover to uninstall it: We can reinstall it when we're done with CF. Note 3: If you receive an error Illegal operation attempted on a registery key that has been marked for deletion, restart computer to fix the issue. Note 4: Some infections may take some significant time to be cured. As long as your computer clock is running Combofix is still working. Make sure, you re-enable your security programs, when you're done with Combofix. NOTE.

If, for some reason, Combofix refuses to run, try the following. Delete Combofix file, download fresh one, but rename combofix.exe to yourname.exe BEFORE saving it to your desktop. Do NOT run it yet.

Download Rkill ( courtesy of BleepingComputer.com) to your desktop. There are 2 different versions. If one of them won't run then download and try to run the other one. You only need to get one of these to run, not all of them.

You may get warnings from your antivirus about this tool, ignore them or shutdown your antivirus. RKill.exe: iExplore.exe (renamed rKill.exe): Restart computer in safe mode. Double-click on the Rkill desktop icon to run the tool. If using Windows Vista, 7 or 8 right-click on it and choose Run As Administrator.

A black DOS box will briefly flash and then disappear. This is normal and indicates the tool ran successfully. If not, delete the file, then download and use the one provided in Link 2. Do not reboot until instructed. If the tool does not run from any of the links provided, please let me know. When the scan is done Notepad will open with rKill.txt log.

RKill.txt log will also be present on your desktop. Once you've gotten one of them to run, immediately run yourname.exe by double clicking on it. IF you had to run rKill post BOTH logs, rKill.txt and Combofix.txt.