Documentation review: · Windows PC · English
Write down the failure first
An exact message and a reproducible action are more useful than saying the program does not work. Record the Windows version, VirtualDJ build and what changed immediately before the issue appeared.
Keep screenshots of your audio settings and any controller mapping before changing them. A reversible test is easier to interpret and safer for a working library.
Download and installer problems
Check that you selected the Windows package and that the operating system meets the current requirements. Use the publisher endpoint rather than a repackaged installer. Keep Windows security enabled and investigate any unexpected publisher or filename.
If a browser download fails, confirm the source and connection. Do not substitute an unrelated executable just because it downloads successfully.
Application and library problems
Use a known local file to separate basic playback from a missing music location or unsupported source. If the library shows missing tracks after moving a folder, inspect the paths before rebuilding everything.
If the issue started after an extension or custom skin was installed, return to the normal interface and test without the optional component. Preserve your original configuration so the experiment can be reversed.
Hardware and audio problems
Controller recognition, control mappings and audio routing are different checks. Verify the device model, required driver and license. A responding play button does not prove that speakers are connected to the selected output.
For silence, inspect deck and master meters and follow the audio path. For headphone cue, test an independent track and check the selected output channels. Use the exact device manual for the connection arrangement.
Online-service problems
Confirm that the intended catalog is selected and the account is authorized. Then test a local file. If only streamed tracks fail, avoid rewriting your working audio configuration as the first response.
Check the provider's restrictions before interpreting an unavailable feature as a bug. Stems, offline playback and recording can have source-specific limitations.
Prepare a useful support request
Include the smallest repeatable example, exact error, build and device details. Describe which tests passed and which failed. Do not share passwords, account tokens or private payment information in public support posts.
Does this guide replace publisher support?
No. It helps organize the evidence. Account, licensing and build-specific issues should be sent to the publisher.
Does the website claim hardware testing?
No. These procedures are documentation-based guidance, not a claim that every listed setup was tested in a physical DJ session.