Update 16S to 17S- Confused by BM's Upgrade Site

I need to upgrade from 16 Studio to 17 Studio as my first install of 16S was lost due to the WIN10 update debacle...wiped out both my boot folders and could not repair....I had a sys image bak, but when I used that DVR asked me for the licence code again , so am now on my 2nd install.
Black Magic state that you should Uninstall 16S before upgrade to 17S, which made me very nervous about losing my Studio licence, so I posed a question on the DVR16 site to confirm what I should do..and got two quite different and opposing replies!
So I went to the BM upgrade site direct, but found the instructions to upgrade from 16 to 17 a bit confusing as well!
Here's their extract:
----------------------------------
Software Update12 Feb 2021
DaVinci Resolve Studio 17 Public Beta 9
This software update adds support for project collaboration and remote database connection on the free version of DaVinci Resolve when using the DaVinci Resolve Project Server. In addition, this update adds new options for applying effects and better composite behavior when cropping images. DaVinci Resolve Studio 17.0 Public Beta 9 also adds faster importing of AAF timelines and more accurate snapping behaviour on the Fairlight page. This version requires a DaVinci Resolve Studio license dongle or software activation code. Read more
--------------------------------------------------------

So I take it if I download the Studio 17 version I just need to input my Activation code?
Is that right? (my previous received advice was that I just uninstalled and didn't need the key)

Please can someone from Black Magic advise me of the correct procedure to download the STUDIO version of 17 so I can replace me STUDIO 16 (8) version which is now corrupted and unusable...I cant re install my 16 S as its on its 2nd install and the only way forwards is to change over to 17 Studio which is allowed by BM.
Also when they say uninstall, I take it you have to separately Uninstall all the other DVRS categories as well? (Fairlight, control panel etc)

And should I use REVO uninstaller which removes all leftovers and fragments or best to use the WIN10 uninstaller first.? (I've already backed up my data bases and all individual projects, about 100 of them.

Please excuse my nervousness as lately if "Anything Can go Wrong..It Has !!"
I me way behind at the moment and need a fast catch up with a properly installed Studio 17
and the last quote I had over her in OZ for another DVRS license was over A$600 !
Don't want to pay for yet another license to get going again.
Thanks for your time
John Byers

– Both a key code or a dongle works for either version.
- Even if you don't first deactivate your key from an older installation, you don't loose an activation.
- The third activation will simply kill the very first one – wherever it is in cyberspace.
– Only exception might be connection problems or server hiccups at BM's, which some have experienced recently.

[Shrinivas Ramani]

Hi John

From what I gather you have 16.2.x Studio installed, and due to OS updates, it is now unusable. So you're looking for recommendations.

1. To start with, let's address the OS updates bit. Windows 10 can update, among other things, graphics drivers.

The required minimum driver version depends on the exact Resolve version. In the support page, select "Find in page", type your exact version (e.g "16.2.8"), click "Read More" and review the minimum requirements - drivers, CUDA and OpenCL requirements, VRAM minimums. Google your card model and confirm these requirements are met. For older nvidia cards, consider sticking to 16.2.6 in the interim - as it has lower minimum requirements for Nvidia cards.

If you have an nvidia card, head to the nvidia driver site, select your model, download the latest driver (studio if one is available for your card) and install it. During installation, you want to select Custom and choose "Clean installation" to avoid remnants of Windows drivers being left behind.

It's a similar procedure for AMD and Intel graphics - go to site, download, install. As a clean option may not be available, utilities like display driver uninstaller can help clean out the current display driver. Installer and instructions can be easily found online.

Finally, to stick to safe and tested graphics drivers, consider disabling Windows 10 driver updates.

2. Now to Resolve startup and update. Since we've updated drivers, try starting Resolve 16 now, using a new project. Chances are that it should work. If it doesn't and you want to try Resolve 17, first back up your databases - for a disk database you can just zip that folder away as a backup, including the exact Resolve version in the file name for reference. Then install Resolve 17. You don't need to uninstall prior versions, just follow through with the installer wizard.

If there are still startup issues, then consider a clean uninstall - including the use of products like Revo uninstaller.

3. Finally, your license worries. It is worth reading through this FAQ section once more. In short, your key allows two activations at a given time. During a new activation, if you already have two activations, you can choose to deactivate all existing licenses - including abandoned machines, formatted disks, corrupt installations etc. You do not lose activations due to technical issues. As I'm drafting this, Uli has beaten me to this licensing info.

Thanks. This should be a sticky!

– Both a key code or a dongle works for either version.
- Even if you don't first deactivate your key from an older installation, you don't loose an activation.
- The third activation will simply kill the very first one – wherever it is in cyberspace.
– Only exception might be connection problems or server hiccups at BM's, which some have experienced recently.

--------------------------------------------------------------------------------------
My thanks to you Uri for your clearly stated info: So I have two installs in perpetuity and a 3rd install merely wipes out the first. That's a great relief and to BM's great credit to allow this. But I wish BM had stated this as clearly as you have, would have saved a lot of angst. Two things threw me on my misunderstanding of BMs statement. First they called the 17 download a PUBLIC beta and referred to the Studio version in the same way. Now PUBLIC means "openly shared by the people" which the paid Studio version certainly is not. It would have been better for BM to have called V17 free as a Public Trial and Studio as a Trial Only version, which could have covered both instance's better.
The second was my re install of 16 via my sys image backup disk, as Resolve went in OK, but then asked me for my license key, hence that convinced me that 2 installs only were absolute.
That should not have happened?
Other wise I would have added another PC to the Studio install which would have increased my through put, instead of running the free version on that one with its limitations (for me).
So a big thank you on that again, Uri.

To the other gentleman who replied:
I keep the latest Nvidia driver for my MSI RTX2080TI 11 GB TRIO installed, though this always downloads as the DCH version and have commented before that the Msoft version, (non Studio) may be installing itself over the Nividia one at update times as GPUZ seems to indicate.
I never run GeForce for that possibility, as games drivers seem to be to be top of the list to install by default from Nvidia when GeForce used,
I have two other PCs with GTX Super cards (1650 and 1660) and both of these also download as DCH drivers....on Win7 (1650S) the Studio driver is not available, only the Games version will install. (Win7 used as some engineering s/ware I have only runs on that...and its reliably stable!)
I keep my GTX1660 older PC (No Nvme) as a backup for Resolve work as it has 8 SATA HDD, also 8 USB HDDs on it, though I can also run it with the free version of 16 to do preliminary edits while the Studio PC does its more advanced stuff.

Thanks again to all who replied and helped me out here. Much Appreciated

John Byers

[Shrinivas Ramani]

John,

The betas are not trials. They are fully functional applications that have been ratified in quality for public release and are often used in production scenarios. Betas follow the same licensing rules as other fully functional public releases. I would add again that the Licensing FAQs linked above cover the exact questions you raised - simultaneous usage, deactivation, number of reuses and other scenarios.

The term beta is commonly used in software to indicate releases where:
• new features may be refined based on real world use and feedback,
• major bugs/deficiencies outside of our test scenarios/platforms can be caught early and remedied, and
• documentation is updated accordingly.

In terms of drivers, the Nvidia minimum driver recommendations have changed recently (explanation). The advice above still holds true.

Regards
Shrinivas

[quote="Shrinivas Ramani"]Hi John

From what I gather you have 16.2.x Studio installed, and due to OS updates, it is now unusable. So you're looking for recommendations.

1. To start with, let's address the OS updates bit. Windows 10 can update, among other things, graphics drivers. ============== etc
----------------------------------------------------------
Thank you for your detailed reply Ramani (Shrinivas)
My current Win10 64 Pro is Build 2021.02.13.18816455 and has been since it was last updated to that by Msoft some time ago
My current GFX Nvidia RTX 2080TI 11Gb TRIO driver is (Studio) 461.40 DCH (Jan22 2021)
I have just checked NVidia site and that's still the latest available Studio driver for that card.
My Resolve Studio version is Studio 16.2.8.005 (no dongle)

I am indebted to you for the link of how to avoid Msoft updating my drivers on the fly.
I've immediately implemented this.

My initial loss of my 1st Resolve 16S was when Msoft changed from 19xx to 20xx , big problems and I had to go back to the older Win version and re install Studio.16.2.7 from a sys image where Resolve asked me to re input my key code. That was some time ago
I upgraded Win10 as above when that version was declared more stable and usable by users.
and have been using Resolve fairly fully on all pages on the16.2 .7 version without major unknown hassles

My Resolve problems only started after the upgrade to 16.2.8.005 from the previous .7 version
Resolve started to deteriorate only after the .8 was installed. Before that it ran fine.
I put this down to the fact that, in all previous versions, the Zip file seemed to be self extracting and installed each upgrade automatically without problems and without having to uninstall first.
However the .8 upgrade zip did not. It had to be extracted with 7Zip (64)
Its only since then that Resolve gradually became unusable.
I've put this down either to a corrupted download or by 7Zip
I didn't re install back to the DVRS V .7 zip as I was under the impression (incorrect as pointed out by others here ...thank you all) that I had only 2 installs and that was that.

Beta Versions: I understand fully the purpose of a beta version (in a past life I wrote assembly progs as add ins for engineering software (PDP11 and Z80/8080) and labelled my own efforts as Beta versions until they were found to be fully working bug free in the field.)
My concern was in the labelling of the (apparent) Studio version of 17 I downloaded as being "Public" beta, with the accent on the "Public".
As I mistakenly thought I was on my last possible install of DVRS, the "Public" designation of the apparent Studio 17 download alarmed me as it logically states its NOT a private Studio version, by the very dictionary definition of "Public" ( means available to all)

I intend to Install and run the 17 beta version instead of 16 due to the very impressive features in this Beta version and am willing to put up with stability risks till its fully cleared.
So shall be installing the 17 Zip (Public?? ) Studio version, downloaded from the Studio box from BMs site., this to be installed after uninstalling 16, now that I know ,( thanks to all again) that I can safely do so without de licencing myself

John Byers

[Shrinivas Ramani]

I'd suggest that fixing the driver issues - preferably using a stable Nvidia Studio driver (cleanly installed) - is the first step you want to take.

It is worth searching the difference between Studio, game and DCH versions.

Once you are satisfied intrinsic stability issues are taken care of, you can consider upgrading - either from 16 to 17 (or 17 Studio), or just to a newer 17 release. Please take a look at my response to this gentleman