Try and Decide ...
If Windows (8/8.1) is installed on an empty HDD it may well use the GPT files system. However, if the disk is already MBR even if you do a refromat of the HDD on installation of Windows it will sti have MRB.
I have many Windows 10, only 3 that have UEIF motherboards. None of the have a UEIF partition - I suspect it would only be created if I set boot mode to 'fast boot' in the 'BIOS'.
Ian
So you think T&D will be ok, if you set "normal boot" in stead of "fast boot" in bios ??
It is interesting to note, that 3 people responding on this thread, are using the Samsung 840 Pro SSD. And it appears that all three are having "issues" with Acronis 2016 Try & Decide ....
1. Joseph Zorzin
2. Piet
3. Mathew BrownAnna (Trifonova) Forum Support Engineer, are you seeing this ???? Chime in if you wish please ..............................
Robert Wagner
Black River Computer Services
Cape Coral, Florida
Robert, I don't yet have this issue - I'm avoiding it by reviewing the discussions before upgrading. I've been burned too many times by rushing into upgrades so now I almost always review discussions first. I've had other issues with ATI- including disliking the ATI 2015 UI- but, ATI has saved me several times too by accomplishing full restores.
Joe
An observation...After a failed attempt of making ATI 2016 Try & Decide to work in fresh install of windows 10 I tried to restore the windows 8 image via ATI 2016 but to my amazement & dismay I found the duplicate boot files scattered on to my non system disk and when I deleted the duplicate entries the system became unbootable. This is an unheard & unlikely kind of behaviour from Acronis never in my life have I experienced such anomalies from such a reputed programme. Could this be due to incompatibility between ATI 2016 & Windows 10 or is it that Acronis has gone totally wrong this time? Hoping the next new build of ATI 2016 might resolve all the issues.
Piet, I have no idea. Merely making an observation that may help someone work out what its going on.
Ian
Tried to restore a backup of partition C, WITH SYSTEM-PARTITION , I got a warning from ATIH, so never try to restore the systempartition from your backup, only the ( much bigger ) C-partition,with Windows on it.
If doing so,this never failed and the backups are 100% accurate,as far as I know !
Maybe coz this GPT-format ???
My SSD is a SEAGATE ST240FP0 (223 GB) and it is formatted as a GPT disk.
Hi All
As far as I can remember, choosing UEFI in the boot setup forced me/Windows 8 to use/format the primary disk as a GPT disk.
I then did an inplace upgrade to Windows 10.
Am I wrong in thinking a GPT disk is NOT a Dynamic disk?
In all the discussion, GPT is supported by Acronis True Image. No mention so far of the official response to UEFI. (or did I miss that)
I can and have done, booted from the Linux boot disk created by True Image 2016.
I have also restored using that disk.
So in that part of the program I'm happy.
Its only Try & Decide that fails to start, stating that the disk configuration is not supported.
Its not a deal buster, 2016 is a bit faster than 2015 and has facilitys that I havent tried yet like the family dashboard.
(I will be trying that soon to see if it integrates with 2014 or 2015 versions).
True Image 2016 works on my pc for backup and restore for bare metal backups and restore, which is what I want.
Hopefully as we have been Beta testers, our requests for minor changes will have weight and be implemented.
However with no feedback from the firm themselves its a bit frustrating.
It would be nice to know someone reads these and whether our comments are welcomed etc.
Mike
Paresh,
When you restored, did you have many other partitions in the PC? Had you moved the around physically?
When you did the restore, did you check the sizes etc of the source and destination?
I did notice when I did a couple of restores that I had to do one partition at a time to ensure I copied the correct backup to the right partition/disk.
Its mainly a problem when you have many disks/drives and move them around AFTER you have done a backup.
True Image assumes when restoring that the disks will be in the same position.
I have noticed also that windows shows my drives, (in Disk Management) in a different order to the motherboard connections
Mike
I can not find GPT-format on the supported-list !
You talk about Win8, but on my system its Win7, when installing Windows it "sees" the SSD and its been formatted with GPT, at least the systempartition.
My bios is in EZ-mode , dont know how to chance this , but I have never heard someone saying; I can reboot in T-modus ,with clicking on "CONTINUE"!
This is a prove ,ATIH2016 still not compatible with SSD/GPT and modern UEFI-bios ! After latest update (today!) ,same problem,they did not fix it yet.
Indeed, backing-up and restoring goes very fast ( 3 minutes !), a real good point for keeping the program, but when needing T&D if a reboot is required ( in Try-modus !!), you will not succeed,coz only "DISCARD" will bring you back in Windows again !!
Patience and more patience, maybe someday it will be solved.........
Mustang .. your post and comments are very well put. I am still reading thru so to understand completely. My compliments to you on your professional expertise.
So, we have at least 5 Samsung 840's that have issues .... sorta makes you wonder what is inside that little box that is different.
I am STILL wondering why MY system will not start T&D !! I am running a 1 Tb Western Digital WD10JPVX-22JC3T0 drive ..
BTW Carlo, Shadow Defender works just fine on my system too .... interesting ..
Awaiting your results Mustang ......
Robert Wagner
Black River Computer Services
Cape Coral, Florida
Hello everyone,
I have been following this thread with some interest in hopes to find the time to perform some tests on my Test Bench machine. For those interested the machine is one of my custom builds using an ASUS Z97 Deluxe motherboard, 16GB of G.Skill DDR3 2400 XMP Ram and overclocked to run the XMP profile at 2400Mhz, Intel i5 4690k CPU, and running an assortment of SSD, HDD combinations. There are a total of 8 drives presently at my disposal in the system however all drives were not attached in these tests as can be seen by viewing the attached Windows Disk Management (DM) screenshots.
I ran tests using a Win 7 Ultimate X64 install on a Basic MBR Style 120GB Mushkin SSD and also on a Win 10 Insider Build 10525 X64 on a Basic GPT Style 240GB Mushkin SSD which was created using an Acronis True Image backup file made from a 120GB Mushkin SSD source disk. These 2 OS installs are bare minimum installs meaning that there are no other software installs other than True Image 2016 on either disk so interference from other software is not a question/possibility here. The only other drive attached to the system during testing was an LG 16X Blu-Ray Burner drive SATA attached and in the Win 7 tests a flash drive to capture screenshots but neither should have any effect on my results.
Additionally, upon startup of the Acronis app this morning I was greeted with the Update Available notification as I have Search for Updates Automatically enabled so I decided to go ahead and Update the application before running these tests. The Upgrade was performed on both Systems Disks to allow for an equal comparison between the two. The Update is officially HotFix 1.
In my first test I used the Win 7 installation to start Try and Decide on the machine which was successfully started. I followed Roberts lead and created a single folder on Desktop and additionally I created a small text document and saved such to my Documents folder. I then choose to reboot the machine which was successful and resulted in the already discussed blue screen selection of Continue or Discard. I chose Continue and the machine restarted successfully to the logon and then to the Desktop without issue. I checked to see if T+D was still running which it was and the folder I had created and the text file were both still present and accessible. I then created another folder on the Desktop and I downloaded a file from the internet and saved it in my download folder. I then chose to reboot the machine. Again I was presented with the choices of Continue or Discard, I chose Continue and once again the machine booted as expected and once logged on all changes made in the prior actions were available. At this point I am convinced that the T+D feature is working on this setup so I chose to reboot once again. When the choice screen of Continue, Discard appeared this time I chose Discard. Machine continued to boot and all changes made to the machine during the T+D session were removed from the machine. So I deem this round a complete success story.
Now the one problem I encountered with the above test sequence that is only an as interest point is that on each restart of the machine I would receive an error message stating the True Image Monitor had stopped working. An obvious bug in the HotFix.
My next test of course was using the Win 10 install. Again this on a Basic GPT Style disk as shown in Windows Disk Management. In attempting to start T+D I received an immediate error stating that T+D could not run on a dynamic disk! What? Where? No such animal here that is apparent to me! This was totally unexpected I must say so I clicked on the close option to dismiss the error and once again attempted to start T+D. This time a different immediate error was received which said that T+D could not run when Acronis Startup Recovery Manager was activated! What? Where? I have never started that service on this machine period! This again was totally unexpected so again I chose the close option to dismiss this error. Out of curiosity I decided to run the Acronis Startup Recovery Manager feature just to see what would occur. That service started and became active. Hmmm. strange, you would have thought that if the application deemed the service as already started per the previous error message it would have complained and stated that the service was already running! Not so, so I ended the Startup Recover Manager service and thought I would then give T+D another opportunity to run. No dice! Failed again with the Recovery Manager is running error as stated above! So this test was deem as a complete failure in ways that have not been brought forth here thus far.
An additional note in all tests of T+D, Startup Recovery Manger, and start of the True Image app were all performed by right click context menu, run as administrator so privileges are a non issue as well.
Attached are screenshots of the various items discussed above for those whom care to have a look.
Very surprised it does work(??).
Looks if ATIH does not like the SAMSUNG SSDs, or the UEFI-bios with it !
Piet,
My test machine has the same bios as yours I believe. It is UEFI capable but set to run in CSM compatibility mode so when UEFI is not needed to boot the machine it is not used. I believe this is the default setting in the bios so there may be something with the Samsung drives specifically but I am not sure that is the case here. If it is specific to Samsung EVO drives it would be a controller issue in those drives. As information my Mushkin drives use a Sandforce drive controller.
Piet,
As Robert Wagner has pointed out to you a couple of times, you go not have a GPT system (unless you have changed it since your first post), you have a BASIC MBR setup.
What might be helpful is if you could post what brand and model (if any) your PC is.
Does your system allow you to boot into Windows safe mode?
As Mustang has mentioned, are you able to boot this system with the Linux recovery CD? IF you can't, then not only will you have a potential restore problem, T&D will have problems working correctly.
The other question is, now that build 5576 is out, does that solve the problem?
Do you on your PC have any other disk utilities that run in the background such as Drag2Disk or INCD running?
I haven't read all the post in this thread today as I don't have much time. I do have some additional information to report before leaving for the day.
I reran my test in number 2. (the Windows 10 32 bit MBR system) using a Samsung 850 Pro SSD. This was done with TI2016 build 5518. TnD started and functioned perfectly. I must conclude the problem has nothing to do with Samsung SSD's or SSD's in general. I believe the problem is strictly related to the GPT disk stricture.
I upgraded TI2016 in my UEFI/GPT system used in test 1. to build number 5576 released today. TnD still will not start. No surprise as the build 5576 release notes did not mention anything about TnD being fixed or modified.
I notice some people are confused about the terms UEFI, GPT and MBR. I suggest you do some Googling of UEFI and GPT. It's just too much for me to explain those terms here. In general, UEFI is a BIOS replacement and GPT is MBR replacement. Basic and dynamic disk can exist in both GPT and MBR disk structures.
Windows 8, 8.1 and 10 systems can be either GPT or MBR. When Windows is installed, it will installed in whatever the structure of the disk is before the install is started. A new disk will usually have the MBR structure. If it does, Windows will be installed as MBR. If you want a 64 bit UEFI system, you need to convert the disk to the GPT structure before installing Windows. Only GPT disks are UEFI bootable. This can be done using Microsoft's Diskpart or a third party disk partitioning program such as MiniTool. Most (but not all) UEFI motherboards are written in 64 bit code. As such they will only boot 64 bit systems on GPT disks in UEFI mode. MBR and 32 bit systems can be booted in Legacy or CMS mode on these motherboards. That's all for now. Study up if you want to understand these term better.
Yes Mike I have three internal drives each partitioned into two, the HDDs are Seagate 500 GB, Seagate 1TB & Western Digital 2 TB respectively. I've been using these drives in the Windows 8 Pro 64 bit environment with Acronis True Image Premium 2014 Build 6688 without a hitch. Lately I tried the latest ATI 2016 Build 5576 but to of no avail, it is as if I've hit the wall & there seems to be no going beyond that point. By default my boot mode is legacy, I tried switching back & forth from legacy to UEFI & UEFI to legacy. True & Decide still did not work but in the process my system became unbootable, Luckily I had taken another backup with Terabyte Image For Windows which came to my rescue. I had very high hopes that the new build would resolve all the pending issues of Try & Decide mode but what a disappointment it turned out to be. Almost on the verge of giving up on ATI 2016 unless someone comes out with a miraculous resolve.
Mustang, thanks for the brief overview of UEIF. My three systems with UEIF motherboards must be booting in Legacy or CMS mode as they are all on MBR disks. I am running ATI 29016 Cloud on each of them.
Ian
OK Colin here we go, we are on Win7x64 Pro,ASUS-motherboard Z97-K ,i7-Intel-processor,32GB RAM, SAMSUNG 250GB SSD,2x WD 1TB each.
OS installed on the SSD, BIOS in EZ-mode,fast-boot,partional USB-support,all drives AHCI-supported,no RAID but OC ( dont know what OC means,can not find it ! But if on RAID no normal boot,so I kept it on OC(?)
I do hope you know more now.
T&D starting up fine,but can not use Secure Zone for T&D anymore ! ATIH2014 always used Secure Zone and went perfect on HDD .
Im able to apply/discard chances inside Windows, and also after restart it does.
The boot-cd works great, fast backups/restoring also.
Only reboot in Try-mode ,by clicking on "CONTINUE" not possible on my system.......
The latest update did not chance anything.
I believe the issue here is simply that of the GPT partition STYLE. The GPT STYLE allows for both MBR STYLE partition and Dynamic partitions to exist on the same disk. The MBR partition on a GPT STYLE disk is described as a Protective MBR and contains the partition table for the boot volume. The GPT partition STYLE also contains a Primary GUID Partition Entry Array which acts as a partition table for the GPT partition STYLE. The GPT STYLE allows for up to 128 Primary partitions per disk where as the Basic MBR Partition STYLE allows for a maximum of 4 Primary partitions. The GPT STYLE also contains a Backup GUID Partition Entry Array at the end of the disk which is also a requirement of a Dynamic disk. Because of the layout of a Basic GPT disk such a disk is dynamic in nature thus the T+D feature detects that the disk is dynamic.
So at the end of the day it appears at least to me that Try and Decide will work for you if you are using an MBR STYLE Basic disk. If you are using a GPT STYLE Basic disk however because of the nature of such a disk being dynamic Try and Decide will not function.
Ran it from my Windows 10 32Bit partition and it works perfectly.
Both partitions (32 and 64) are MBR Basic (partition is 0x07).
So i guess it's simply a matter of compatibility on 64bits.
It should be compatible with 64-bit also,according Acronis !
64 bit has nothing to do with it. It is the detection by Try and Decide of the presence of a dynamic disk that cause it not to run.
So, why it runs on w10 32 and not in w10 64, both partitions basic MBR?
The system -partition ,made by Windows during the installation of Win7 x64, is " ACTIVE" does that mean " DYNAMIC" ??
Its a Samsung SSD 850 Pro 256GB SCSI Disk device. This system-partition is 100MB and only made for the system, its the only "ACTIVE" partition in this PC. The other two HDDs are for media etc. ,and are all basic/primary.
I can not find the word "DYNAMIC" ,ONLY "ACTIVE" !!
Just to avoid other misunderstanding (check image)
Disk is BASIC MBR.
It's not GPT.
It's not Dynamic.
That's it.
Moreover, my bios doesn't have any UEFI option (it's simply too old for that, GA-X58A-UD7 rev2.0 Motherboard).
C.
is " ACTIVE" does that mean " DYNAMIC" ??
Active is a flag that tells the BIOS/UEFI which disk to boot from. Remove the flag and you will get a 'no disk found' or similar error message.
From the information given, you do not have your system set up as a RAID nor using any of Microsoft's advanced disk setups such as Storage Spaces, therefore your system is NOT set up as dynamic.
IF you want to be doubly sure, take a screen/snipshot of Windows Disk Manager and attach it to a post here. We will then be able to tell you categorically how your system is set up.
Ok ,Colin, please,look at thes snapshots ,and tell me then if my system is compatible with T&D .
Joseph, Piet, Mathew, Carlo and everybody else, who experience similar problems using Try and Decide feature, please contact our support team so that we can investigate the problem and confirm/not confirm that it is related to particular hardware.
Mustang, thank you for your dedication and invaluable help!
Piet,
Thanks for posting the screenshots of your system. It appears that your installation does not involve dynamic disks. I did notice that your partition named Image drive G: is marked as an active partition. It does not appear to contain any operating system and I would not think that it contains any boot records. If that partition is only for data storage it would be wise to remove the Active flag from that partition. There should only be one active partition on your machine. This condition might be confusing T+D so could be the source of your issue.
Carlo,
Not sure why your problem exists, I would take Anna's suggestion and contact the support team with your issue.
Hi Enchantec, on Image G ( WD-1TB HDD) are all my Acronis backups, and Windows backups placed.
I did not make this partition "active", so I guess Acronis or ,maybe,Windows marked the G-partition "active" ??
Whats going to happen if I make this partition "primary basic" ?
Can I still use my backups afterwards ??
If its no problem, will try it, if it could solve the problem !
Removing the Active flag from that partition should not cause you any issues with using the disk. The active partition is the primary partition on a hard drive that typically contains and boots the operating system. Since partition G does not contain the operating system you should not have any problem.
If you look at the first partition on Disk 0, Reserved partition you will see that it is also marked as Active. This is correct for a typical installation. The Active flag tells the system where to look for the boot files.
Enchantech, did as you said, removed the volume G, made a new formatted partition G ,this time primary/basic, so not "active" anymore.
Reboot in Try-modus, and same problem, only restart in Windows with "DISCARD" , choosing "CONTINUE" gave me this endless restart again.
Conclusion; this is not the solution for solving this problem !
After days in this forum ,still no solution and a real bottleneck what makes T&D not so good as it used to be !
imo; ATIH not compatible with SSD,EUFI,64-bits, I STILL DONT KNOW!!!
It is a mystery to me as well for your problem. I suggest contacting Acronis support and send them a system report.
Yep,so I did already,several times, I only get "casenumbers" and promises they will contact me within 2 days ; NO ANSWERS AND STILL NO SOLUTIONS AT ALL !!
They better be honest ; tell the truth; ATIH2016 NOT COMPATIBLE WITH SSD/EUFI etc.
I could live with it,and wait for updates ( miracles?), but all these promises are making me real sick.............
Enchantech, did as you said, removed the volume G, made a new formatted partition G ,this time primary/basic, so not "active" anymore.
Reboot in Try-modus, and same problem, only restart in Windows with "DISCARD" , choosing "CONTINUE" gave me this endless restart again.Conclusion; this is not the solution for solving this problem !
After days in this forum ,still no solution and a real bottleneck what makes T&D not so good as it used to be !imo; ATIH not compatible with SSD,EUFI,64-bits, I STILL DONT KNOW!!!
Does ATI 2014 work with SSD,EUFI,64-bits? If so, why not install that? or is 2015 and 2016 needed for W10?
Joe
Only ATI 2015 (latest build)/2016 are claimed to be Win 10 compliant by Acronis. But then....
Ian
Thought I would post an update to this thread hoping it might help clear up some confusion about this issue.
In the tests I ran for T+D my Win7 Basic MBR installation worked as expected. My tests using my Win 10 Basic GPT installation failed due to detection of disk as being dynamic.
The sole reason that the test failed on my Win 10 install is because the partition structure of that disk is dynamic. The disk contains a total of 5 partitions only 4 of which can be viewed in Windows Disk Management. The partition that cannot be viewed is known as the MSR or Microsoft System Reserve partition. This is a hidden 128MB partition that must be placed on disk ahead of the System partition in the partition structure.
Had the above installation been done without the use of a default standard GPT STYLE/SCHEME then it no doubt would run the T+D feature/function.
So it is not enough to simply view Windows Disk Management and look at the description provided for a disk as is in my case shown as a GPT Basic disk. This only describes the STYLE/SCHEME of the disk but does not convey the partition structure which is the key factor that must be known in order to determine if your disk is dynamic or basic.
The only way to view disk structure is with third party tools or Windows Diskpart. If you are unfamiliar with Diskpart do a google search and read the Windows Technet articles for more information, use at your own risk!
Below is a great article to understanding disk partitions, worth the read.
https://technet.microsoft.com/en-us/library/Dd799232%28v=WS.10%29.aspx
Many thanks for this link. I read it with great interest.
It seems to be directed more to OEM and enterprise users rather than home users such as myself.
Ian
That is true however understanding the basics is key to the end user in understanding the capabilities and limitations of their devices and services and applications they wish to run on those devices. This article coves a good deal more than the basics true. Glad you had a good read.
Yes, you are correct about that. As most users do not build their own systems, they will have an OEM Windows installation, which if the PC is recent will have the GPT/UEFI setup which seems to be the cause of the problems being experienced by many users.
Ian
Thanks a bunch for your technical knowhow Enchantec but my query still stands, as I had mentioned in my earlier post, my setup is simple & consists of Legacy Simple Basic/MBR boot format {UEFI Turned off by default in the bios} & yet T&D refuses to work Under Windows 8 Pro 64 Bit & on the fresh install of Windows 10 Pro 64 bit {no other programmes installed} Environments. ATI is out with a new build 5586 but still no mention of any changes in Try & Decide, will give it shot & post my observations later.
Here's another good link explaining Basic and Dynamic disks https://msdn.microsoft.com/en-us/library/windows/desktop/aa363785(v=vs… . Most users will have Basic disks on both MBR and GPT partition style disks.
Installed the programme successfully ran T&D changed the theme ,placed an empty folder on the desktop & rebooted selected the continue mode. Wham! back to square "A" windows simply booted back & there was no trace of the personalized theme, empty folder & T&D as if T&D had never started it just simply refuses to survive the continue mode. What frustrating & disappointing results are coming out of try & decide mode even with the latest ATI 2016 v19.0 build 5586 under Windows 8 Pro 64 bit. Is this time to give up on the app or keep trying the new builds senselessly with a hope against hope?
Enchantech .... reference your statement
<>
If what you are saying, is that the MSR is actually a dynamic partition, than that is a very powerful find and statement. Do you suspect that T&D is analyzing the disks partition structure and failing due to the presence of a dynamic partition (MSR), which in most cases is hidden unless a third party tool is used ??
The MSR totally escaped my review of MY partition structure. (See attached). NOW I see that the MSR' file system is simply shown as "other".
The fox is hiding on this hunt, but seems we have a lot of people beating the bushes out in the field ....................
Thanks for the valuable informational article on https://technet.microsoft.com/en-us/library/Dd799232%28v=WS.10%29.aspx
Robert Wagner
Black River Computer Services
Cape Coral, Florida
I can't say it enough:
No GUID, no Dynamic here.
Disk 6, Total Sectors: 234433391, Name: Corsair Force GT, GUID Partition Table: NO, Dynamic Disk: NO, CHS:232572/16/63
letter: * PartID: 0 Start: 0 End: 4095 Size: 4096 FsId: 0 Label: ClusterSize: 1 FreeSectors: 4096 Primary: 0 Bootable: 0 BootVolume: 0 SystemVolume: 0
letter: Z PartID: 7 Start: 4096 End: 234431447 Size: 234427352 FsId: 7 Label: Win7 32Bit ClusterSize: 8 FreeSectors: 89038784 Primary: 1 Bootable: 1 BootVolume: 1 SystemVolume: 0
letter: * PartID: 0 Start: 234431448 End: 234433390 Size: 1943 FsId: 0 Label: ClusterSize: 1 FreeSectors: 1943 Primary: 0 Bootable: 0 BootVolume: 0 SystemVolume: 0
Disk 7, Total Sectors: 488397168, Name: Samsung SSD 840 EVO 250G, GUID Partition Table: NO, Dynamic Disk: NO, CHS:30401/255/63
letter: C PartID: 7 Start: 2048 End: 488396799 Size: 488394752 FsId: 7 Label: Windows 7 Ultimate 64bit ClusterSize: 8 FreeSectors: 245787944 Primary: 1 Bootable: 0 BootVolume: 0 SystemVolume: 1
Disk 6 contains the boot record (and win10 32)
Disk 6 contains W10 64 (the one where T$D doesn't work).
As you can see there are no GUID partition tables at all.
I now its no consolation that T&D doesn't work correctly for UEFI / GPT disks, but in all of my tests, the one thing that gives me some satisfaction is knowing that a True Image backup and restore not only works, but is fairly fast.
In some ways that makes up for the fact that on my system, and others that Try & Decide does not work.
It seems fairly conclusive as Enchantech states, that for those that follow the trend for UEFI partitions and the inherent safety features (I hope) T&D does not currently work.
I wonder how many others posting here have only tried the T&D function WITHOUT trying the backup and restore function.
I'm retired now, but all my working life, the one thing that always seemed to be true was that testing the backup is a fairly unusual action.
So for me, I'm happy that if I do a backup first, if I install something that screws up the installation, I can get back to normality.
Yes T&D is something I always wanted to rerturn, but for now I can live with the fact that Acronis is working on it.
So to all those that its not working for, Back and Restore to check you HAVE a working backup.
Robert,
I had not thought of this in quite the same terms as you have put it above but yes, that is what I am saying in essence. I am not sure why the MSR partition would trigger this response in T+D nor if in fact it truly does. It might be the remaining partition structure of the disk that triggers the dynamic disk detection.
I do know this: T+D creates a sandboxed space on the system partition in which to run which is a virtual space and as such is dynamic in nature. Acronis System Recovery Module works the same way and it is obvious that these two features cannot run at the same time as evidenced by the errors I received and posted screenshots of in my original post. I would suspect then that if a user were for example running a VHD on the disk that contains the primary system partition T+D would error out as the disk being dynamic as well.
My previous post was an attempt to point out that MBR and GUID/GPT are partition styles or schemes that are nothing more than descriptors of the partition structure on a disk. My theory is that it is how the partition structure is laid out on a disk that triggers the dynamic disk detection of T+D. Both of these partition schemes have a rule set in place which is as follows:
Quick Comparison of MBR and GPT
MBR supports a maximum of four primary partitions
GPT supports 128 primary partitions.
MBR supports 2 TB partition size.
GPT can support 19 EB (19,000,000 TB) partition size.
MBR has no backup partition table.
GPT has backup partition table.
The one aspect of rule for MBR left out of the above is that the forth primary partition allowed in the MBR scheme can be converted into an extended partition which can contain additional logical disk volumes. The nature of doing that is also dynamic. It would be interesting to know if a basic MBR disk that contains an extended partition would also be flagged by T+D as a dynamic disk. I suspect that it could be and if so I in turn think that my theory of it being the partition structure of the disk that triggers the dynamic disk detection to be correct.
I have some good news. I got TnD to function properly on my Windows 10 64 bit system that is on a GPT/Basic disk! My previous attempts to start TnD on this system were done choosing a second internal HDD to store the changes. That disk was a MBR/Basic disk. TnD failed to start with this combination. Today, I installed another internal HDD that is initiated GPT/Basic. TnD now functions as expected.
I was able to start TnD. I installed a new program. I manually rebooted and chose the Continue option. Windows booted properly and TnD was still running. I right clicked the TnD system tray icon and selected "Apply changes with a reboot." The system rebooted and applied the changes then rebooted again into Windows 10. The changes were successfully applied and TnD was now off as it should have been. This was a great result.
These tests were done with TI2016 build 5586 installed. The system was on a Samsung 850 Pro SSD and the internal drive to store the changes was on a HDD.