The whole process, start to finish, including the parts that trip people up.
Open the title's page, press the download button, wait for the transfer, unpack the archive, read the install steps on the page and follow them in order. There is no waiting page, no survey, no shortener and no account. If a site is asking you for any of those, it is not this one.
Every title has three routes: two direct mirrors on separate continents and a magnet. Direct is faster to start and simpler. Pick the mirror closer to you first, and if it is slow, try the other one before assuming the problem is your connection.
The magnet is the better choice for anything above about five gigabytes, or on a connection that drops. A dropped direct transfer resumes if your browser or download manager supports it, but a magnet handles interruption without any help at all, and it verifies every piece as it arrives.
Archives are packed with a standard archiver. Unpack to a folder on a local drive, not to a network path and not straight from inside the archive viewer, which is where a large proportion of failed installs come from. Avoid folder paths containing spaces or accented characters for the larger creative and engineering suites, since several of their installers still handle those badly.
None of the archives on this site carry a password. If you have found a copy of one of our releases that asks for a password, it did not come from here.
This is the single most common question and the answer is always the same. A build whose licence check has been rewritten is, at the file level, a modified executable that behaves in exactly the way scanners are built to catch. Every scanner flags it. That is not evidence that a particular copy is bad, and no amount of rebuilding will change it.
What to do: suspend real time protection for the install, run it, then switch protection back on and add the installed program folder as an exclusion so it is not quarantined later. Do not leave protection off afterwards.
Read the install steps on the title's page before starting. They are written per release and the order matters. Common points across most of them:
Check the comments on the title's page first, since someone has usually hit the same thing. If it is new, post it there or use the contact form. Include what you installed, what happened, and what the machine is running. A report that says only that it does not work cannot be acted on.