For ease of use and be able to pull a scan at any given second given a VIN or license number, i usually save my scans of all my tools in a specific made desktop folder ( with a license plate number and where possible with the customers phone number ). It takes couple extra clicks but it s always visible. I wonder what would it take if in the process of installing VCDS the logs folder would be made visible on desktop ( as you install the vcds ). Perhaps with a name like VCDSLOG or something ?The "Logs" folder will contain all USER saved data, while the "Scans" folder will contain all AUTOMATED/BACKGROUND saved data/scans. If a given scan exists only in "Scans" it implies that the USER never actually/intentionally saved it. Consider the "Scans" folder your "in case of emergency" location, because that is what we intended it to be as we know users tend to be lazy...
Always actively save your Auto-Scan results, then it will be in "Logs" as expected.
While I cannot speak for Uwe (and therefor the English installer/version), some of the non-English installers already have an option you can select during install.i only speak a little English, Romanian ,bit of Spanish ( learned that in the USA of all placesJust create your own "VCDS Logs" shortcut on your desktop, we won't do that automatically as adding stuff to people's desktop is generally frowned upon these days...While I cannot speak for Uwe (and therefor the English installer/version), some of the non-English installers already have an option you can select during install.
)
( hint hint )"Needed"? Or "Recommended"? New versions generally recommend checking for firmware updates whether you need 'em or not.I updated to 25.3.2 and it told me I need a firmware update,
It might be because 25.3.2 is actually newer than 25.7.0. It was an interim branch release that added support for MY 2026. Don't worry, there's a 25.9.0 waiting in the wings.Also I see there is Beta 25.7.0 available, can be downloaded from your website, but not from VCDS software - is that meant to be like that?



We use essential cookies to make this site work, and optional cookies to enhance your experience.