Migration of the Seagate DiscWizard Advanced Capacity Disk to a normal GPT partition

I recently switched from Sagate’s OEM version of Acronis True Image called “Seagate DiscWizard” to Acronis True Image 2020. It resulted in the setup routine detecting the OEM version (which is according to Seagate’s Knowledge Base from 2013)

 VirtualDiskSetup.msi will work in Windows 10 yes, but according to Acronis support this driver is from Windows 8 and not officially supported in Windows 10 and end of life since 2013.

So how can this be resolved?

From an email to Acronis Support in which I described how I have done it:

so I have continued on this as circumstances changed a bit:

I decided to get an addtional SATA III controller to put in an empty PCIe slot I still had in my computer and put an SSD onto it.

So here is what I have done:

As the HDD in question was 6 TB, 4 spread across 2 partitons with the Seagate DiscWizard Extended Capacity Manager and the 2 TB accessible on the front of the HDD was the Windows 10 system disk, I have done the following steps so far:

1) I have tried True Image 2020 Clone Disk Wizard, but as the new SSD is 1 GB smaller than the HDD (due to the nature of SSDs), I got warning messages saying there might be the possibility that Windows cannot boot after the clone is done as the destination disk is smaller than the source.
Despite I answered twice to proceed anyway, after the 2nd confirmation, the Clone Disk Wizard window simply closed without any further message on the screen.

So I gave up on this and instead used the free version of EaseUs Partition Master and cloned the 2 TB Windows 10 partition of the 6 TB HDD to the 2 TB SSD.

2) After that, I added the cloned Windows installation on the SSD via EasyBCD manually to the Windows 10 boot menu.

3) I booted my PC into an old Windows 7 installation I still have and disabled the Extended Capacity Manager. then I went to the Windows own disk manager and removed the 2 TB partition and then used EaseUs Partition Master to remove the 495 MB recovery partition too as windows own Disk Manager would not because of “not enough free diskspace to perform operation”.

4) Then converted the undefined partition from MBR to GPT.

5) Opened the Seagate DiscWizard again. A notification window poped up stating “No Extended Capacity Partitions found, you can partition the disk using “Add New Disc” functionality.

6) “Add New Disc” —> Was able to create a full 6 TB GPT partition

7) Booted back into Windows 10 onto the SSD.

8) Opened Acronis , went to recovery, said disk from the previously backed up extended capacity “Disk” stored on my NAS, to the unpartitioned 5.55 TB disk. However after 40 minutes of waiting, no activiy on the disk even. So I aborted this try and now create 2 partitions with EaseUS Partition Master that are both 3 TB and try again but this time recovery from partiton to partition instead.

I hope this will work!

Not quite the way it was supposed to work and I still have no idea why the clone disk wizard of True Image 2020 left me hanging with no clue, but it is busy recovering now

You are doomed when you have to report a bug to Apple – Here is why.

As a product and software tester myself, I am aware that products have bugs. Apple is not left out of this problem.

It all started in 2017 when I got myself an Apple Watch Series 1. 4 weeks into using the Apple Watch, I noticed that the feature to auto unlock my Apple Watch when I put it on in the morning and lift my arm and turn my wrist, no longer worked. So instead of my notifications, it would ask everytime to unlock my watch, which meant I would miss all notifications which is kind of bad as this is the whole purpose of having a smartwatch. I have tried 3 weeks in resolving this issue together with support after initally sending a bug report. Mind you, no solution was ever found.

So 4 weeks into the problem I lost my temper and patience and decided to resolve it by totally disabling the feature totally. I knew since it was a problem the day I did after applying the latest WatchOS that it must be a software issue, not a hardware issue.

Disabling fixed it in the way that I had to enter the pincode of my Apple Watch to unlock it for the whole day. And each time I received a notification vibration, I tapped the screen and it would light up and show the notification.

Now let’s step into my momentary problem with iOS 13, since day 1 of the update, I ran into massive problems with the iPhone Mail app. I explained this to Apple support yesterday the following way:

Hi there. I Reported bug in support chat 100912882154 on sept29th: What happens since the first release of iOS13 is, that emails that are received and have the same recipient and sender email address, are now displayed in the receive AND the Sent mail folder in the iPhone email app. Which is a huge problem, since almost all Internet-of-Things-devices that send status reports via emails out, do not allow to set sender email address, only recipient email addresses.

I was given https://support.apple.com/HT207132 as a work around which is of course BS as this does not solve my problem AT ALL!

With iOS 12 and below, emails from my devices where only appearing in the received mail folder (aka Inbox) AND NOT as unread emails in the Sent Mail folder as well!

Please fix this issue ASAP!

The response from the Apple Supporter for Apple Germany (I know they sit in Ireland) was, that the dev team who does bug hunting sits in the Apple HQ in the US and they cannot communicate with them at all (I was asked in the chat support conversation in September, to report the bug via the form https://www.apple.com/feedback/iphone.html which of course I did! At the time of writing this, we are now at iOS 13.2.2 and nothing has been done about the different and nasty Mail App behavior. I have the same email address and setup since I first used an iPhone 3g in June 2008!
And unfortunately network devices do not allow you to setup a different sender address than the recipient, so both FROM and TO email addresses are always equal.

Whoever decided to change the behavior in iOS 13 did not take this into account.

Also, the filter suggested is not possible to set, even if it was, it would only change what would display in the iPhone Mail App once enabled via a toggle switch, but the dupe emails would still be stored on the IMAP mail server, stuffing up my email quota for no use.

Also, since AOL Mail does not support advanced filtering like GMail does, there is no solution here.

When I asked the supporter that I don’t want the bug report to be ignored and the bug fixed as it happened with my Apple Watch bug, he said if I think he lies to me, I can ask to talk to his supervisor. Not helpful at all. I ended the chat session then. No need to talk to an uneasy supporter who goes into the rude tendency.

It will probably be like in the Apple Watch case, it will either be fixed with iOS 14 or never at all.

So, I implemented a workaround in Opera Mail, with a filter and every couple of days, I would delete the emails falling under the filter.

Now you wonder, what happened with my Apple Watch bug that I reported 3 years ago? They fixed the problem by simply removing the feature from the Watch altogether! when they released WatchOS 6.1 for the Apple Watch Series 1 😀