Win 10 1709 upgrade to 1809 with E8.5 WG

[Peterjames]

I am considering upgrading my Win 10 Pro edit PC from version 1709 to 1809. I will probably do this using an ISO downloaded from MS and use to upgrade and tick the box to 'Keep personal files and Apps'

Will Edius 8.5 WG still run okay after the upgrade or will it lose the activation data and need reactivating or will the upgrade not interfere with Edius?

The edit PC is normally offline so I do not want to deactivate and reactivate unless absolutely needed. I originally activated Edius 8 WG offline but not sure if it can be de activated offline?

Full system backups/images will be made before upgrading windows just in case there are problems. Thanks Peter

[Jerry]

Since you have been running 1709(October 2017) for a while, I would suggest waiting until 1903 is released. This should happen between now and the end of April. I would also suggest doing a clean install of 1903 instead of an upgrade.

Over time, Windows stores files to which you do not have access. These build up and can 'bogg down' your system. I'm running 1803 and was going to do a clean install with 1809. With 1809 having major issues I decided to hold off.

The one thing I will also suggest, is to clone your system. Having a clean clone not only gives you the best Virus and Maleware protection, it also allows you to update your system without risk, and using it to clone your system drive will keep the drive clean of those pesky built up files.

This is computer maintenance 101.

Drives are cheap. I bought a Samsung EVO 860 500GB SSD for $77 and a Crucial 500GB SSD for $57. I've been using the Samsung Migration software to clone my drive when the destination SSD is a Samsung. This works quite well. I'll be doing a clean install when 1903 is officially released using these drives.

I know this sounds like a lot of work and it is, but doing a clean install from time to time is an excellent option to keep your system working smoothly, IMHO.

[David Clarke]

I have been using 1809 for ages and only had one minor problem related to it - with a laptop where the power saving software would not dim the screen on batteries with 1809 and it did with 1803.

I must say, I do edit with EDIUS 9 all the time, rather than EDIUS 8.

Although, with a new one round the corner it is probably best to wait as Jerry suggests.

[Peterjames]

Thanks to Jerry and David for your helpful advice.

My system has a 250GB Samsung 960 M.2 NVMe fitted to the Motherboard for the OS, not sure how to clone that. I have cloned my previous systems with SSD drives quite easily. Will do some research on the Samsung site. The PC is only used for editing so may decide to leave it on 1709 and upgrade later. Peter

Edit: My Asus TUF X299 Mk2 MB has a spare M.2 socket. Just need to order another Samsung M.2 drive and clone. Should I keep to exact same model and size of drive to avoid any activation problems with software etc ?

Edit Update; Have decided to play safe and order same model 960 M.2 as currently installed.

[Geoff_C]

Peter;
The 'clone' drive is external to the donor pc. Windows does not seem to like having two identical versions of the OS on the same pc. Best to deactivate Edius before cloning otherwise you can loose an activation.
After cloning I normally swap the drives and test the clone. Reactivate Edius.
Assuming all is well I leave the clone in place, then label and stored in a safe place.
G

[Peterjames]

Thanks Geoff.
I was only planning to fit the 2nd M.2 NVMe drive for cloning and then remove the original drive and fit the new drive in its place. Peter

[JohnnyD]

My system has a 250GB Samsung 960 M.2 NVMe fitted to the Motherboard for the OS, not sure how to clone that. I have cloned my previous systems with SSD drives quite easily.
currently installed.

I bought a M.2 adapter to SSD SATA Enclosure . Works good. Cheap.

https://www.newegg.com/Product/Product.aspx?Item=9SIACJF85W4505&Description=m.2%20adapter%20nvme&cm_re=m.2_adapter_nvme-_-9SIACJF85W4505-_-Product

[Peterjames]

I bought a M.2 adapter to SSD SATA Enclosure . Works good. Cheap.

https://www.newegg.com/Product/Produ...4505-_-Product

Thanks for your input John.
As I said in my earlier post I found my motherboard has a 2nd M.2 NVMe socket so I can use that for cloning, however some boards only have one M.2 socket so your alternative could be useful. There are also other makes of PCIe to M.2 adaptors available for people with a spare PCIe x4 slot on their MB. Peter

[Geoff_C]

Not sure that PC will boot if two identical instances of windows installed on PC. PC will boot if copy/clone is connected via external data.

Geoff

[Peterjames]

Not sure that PC will boot if two identical instances of windows installed on PC. PC will boot if copy/clone is connected via external data.

Geoff

Geoff, as I said in post 6 above I was only planning to fit the 2nd M.2 NVMe drive for cloning and then remove the original drive M.2 and fit the new drive in its place on the MB.

This is my intended procedure.
When I fit the new 2nd M.2 drive to the MB it will not have any data or OS on it. I will then boot up as normal and use Samsung migration tool to clone to the new drive. Then I will shut down the PC and remove the original M.2 drive and relocate the new cloned M.2 drive in its place. The original M.2 will be stored away from the PC in case needed in future. I will then reboot the PC (using the new M.2 drive) and then upgrade Win10 and software as required.

I am rather confused as I thought this procedure should work okay. I have used a similar method with SATA drives without issue. Perhaps you can enlighten me where I may be going wrong? thanks Peter

[Geoff_C]

I ran a caddy set up with an option to boot W7 or W10 and this worked fine.
Cloned W10 by fitting new SSD in place of W7 and used Samsung migration to clone new SSD. Had trouble booting with both W10 SSD's in place. With only one SSD in place boot was OK. Just removed either one. Found that if I connected new SSD via a USB cable and then migrated the system I could always reboot. With the caddy setup the drives were connected to sata ports so this may have caused the problem. Maybe I was just unlucky.
However; now possessing a 'migration' cable I use it to create the clone.