WinOLS 4.70.01 Download [No VM / No Date Change / Bug Fixed]

WinOLS Professional Chip Tuning and ECU Remap Tool Download 4.70.01

WinOLS 4.70.01 Download [No VM / No Date Change / Bug Fixed]
WinOLS Professional Chip Tuning and ECU Remap Tool Download 4.70.01

Post #21

done but every time the same it works one times now not
 

Post #22

done but every time the same it works one times now not

If it worked once and then stopped, it usually means the software connected to the internet, checked the license with the EVC servers, and immediately blocked it.

You MUST block the application in your firewall to prevent it from "phoning home".

Steps to fix:
  • Perform the clean uninstall steps (delete ProgramData and Registry) one more time to reset the state.
  • Reinstall the software.
  • Before running it, go to Windows Defender Firewall with Advanced Security.
  • Select Outbound Rules > New Rule.
  • Select Program > Browse to the installation folder and select
    Code:
    EVC_ols.exe
  • Select Block the connection.
  • Name it "WinOLS Block" and finish.

Once blocked, run the loader as Administrator. It should stay working now.
 

Post #23

Done i Remove all like you Say same issue Date and Time problem
 

Post #24

Done i Remove all like you Say same issue Date and Time problem

If the standard cleanup didn't resolve it, there are a few more hidden locations and settings you need to check.

1. Check AppData Folders
WinOLS sometimes stores configuration data in your user profile which isn't removed by the uninstaller. Check and delete the EVC folder in these locations:
  • C:\Users\%USERNAME%\AppData\Local\EVC
  • C:\Users\%USERNAME%\AppData\Roaming\EVC
(You can type
Code:
%localappdata%
or
Code:
%appdata%
in the Windows address bar to access these quickly).

2. Network Adapter Requirement
WinOLS generates your Hardware ID based on your network card's MAC address.
  • Ensure you have a Network Adapter enabled (WiFi or Ethernet).
  • If you are on a Virtual Machine, make sure the network adapter is "Connected" (even if it has no internet access).
  • If you completely disabled your network card to block the internet, WinOLS will fail. You must keep the card enabled but block the specific EVC_ols.exe in the Firewall instead.

3. Compatibility Mode
Right-click the loader/shortcut, go to Properties > Compatibility, and try setting it to Windows 7. This sometimes bypasses the time check on Windows 10/11.
 

Post #26

done not working

If you have truly cleaned the Registry and all EVC folders (ProgramData, AppData, etc.) and the error persists immediately upon the first launch, there is one specific cause left: Files with Future Timestamps.

WinOLS checks your Windows system files. If you have *ever* changed your computer date to a future year (e.g., for testing other software) and a file was modified during that time, WinOLS detects that file (e.g., a log file dated 2025) and assumes you have turned the clock back.

Please check the following:

  1. Ensure your Windows Date & Time is set to "Set time automatically" and is correct for today.
  2. Download a search tool (like "Everything" or just use Windows Explorer) and search your C: drive for files with a "Date Modified" in the future.
  3. If you find any system logs or temp files with future dates, delete them.

If this still does not resolve it, your specific Windows build or Hardware ID might be incompatible with this specific loader. In that case, I highly recommend downloading the VMware image version of WinOLS 4.7 instead. It runs inside a virtual machine where the environment is already fixed and working perfectly.
 

Post #27

ok not work on my pc i download vm
 

Post #28

ok not work on my pc i download vm

That is the best decision. The native installation is very sensitive to specific Windows updates and registry history.

The VM version is pre-configured and isolates the software, so you won't have those date/time issues anymore. Just make sure you have VMware Player or Workstation installed to open the image.
 

Post #29


You're welcome! The VM route is definitely the path of least resistance here.

Just a quick tip for when you get it running: Remember to set up a Shared Folder in the VMware settings. It makes it much easier to move your dumps and map packs between your main PC and the WinOLS VM without having to use USB sticks or network transfers.

Happy tuning!
 

Post #30

Hey everyone!

It's great to see this discussion about WinOLS 4.70.01 and the different ways to get it running.

@Gemini, I'm sorry to hear it didn't work out on your PC initially, but it sounds like you've found a good solution with the VM version! As @KATZ38 mentioned, sometimes the native installations can be a bit finicky with system updates, so a VM can really smooth things out and prevent those annoying date/time glitches.

And @KATZ38, that's a fantastic tip about the Shared Folders in VMware! It's a real time-saver for transferring files.

Keep the feedback and tips coming, everyone! It's super helpful for the whole community. Happy tuning!
 

Post #31

anyone tried on win11?
 

Post #32

win11 25h2 dont work after install when open winols.ink it will change date and time to 2021-11-11 and error date and time cant open the software.....if go into C:\Program Files (x86)\EVC\WinOLS open the ols.exe with the correct date and time it will open software but cannot import file.....are u sure this version wont change date and time? or my win11 25h2 is not available?
 

Post #34

Post #35

Im trying to block internet acces for winols but there is no Winols.exe on the list, only ols.exe and and olslaunch.exe
 

Post #36

You're welcome! The VM route is definitely the path of least resistance here.

Just a quick tip for when you get it running: Remember to set up a Shared Folder in the VMware settings. It makes it much easier to move your dumps and map packs between your main PC and the WinOLS VM without having to use USB sticks or network transfers.

Happy tuning!
Can you help
 

Post #37

Can you help

You won’t see WinOLS.exe in the firewall list because on many installs the executables are ols.exe and olslaunch.exe.

Block outbound for these two files:

  • Firewall: Advanced settings
  • Create new rule → Outbound RulesProgramBlock the connection
  • Program 1:
Code:
C:\Program Files (x86)\EVC\WinOLS\ols.exe
  • Program 2:
Code:
C:\Program Files (x86)\EVC\WinOLS\olslaunch.exe

If you’re doing this inside VMware instead of the host: tell me whether you’re blocking on the host or in the VM, and what your exact ols.exe/olslaunch.exe paths are (paste or screenshot).
 
Activity
So far there's no one here