Please, read my post again. I've been on the fast ring since Jan 2015 so I think I can handle it just fine. I'm not afraid of any risks or breaks, all my stuff is backed up. My theory is based on the facts mentioned above and my copy of Acronis works just fine for my needs.
Thanks for the advice and no need for you to reply anymore. Bye.
"Build 17046 is the first one ever (since January 2015) to failed in both my 32bit and 64bit machines, therefore I think Microsoft is purposely blocking and/or phasing out old hardware not using UEFI bios and/or GPT mode. That would explain the huge amount of failed installs reported since Build 17025."
This is complete nonsense. Old builds may be an issue but whether UEFI or legacy bios has NOTHING to do with it. There is no deliberate policy here but one cannot really expect MS to pay attention to making sure Insiders works on old devices ad nauseam!
If MS was deliberately doing this on old devices, they would simply give an error saying hardware is not compatible.
My FINAL WORD on the subject!
EQuito,
I am running 2 machines. One is a bit newer, a Dell Inspiron 15 machine with UEFI that originally came with Windows 8, and was manufactured sometime in 2014.
The other machine (a desktop) I have is a home built machine, with a Core is 965 EE CPU and an eVGA X58 Classified 3 motherboard with 12 GB of DDR3 RAM. In my profile, the old desktop is listed as my primary machine, with full specs, and the laptop is listed as the second machine.
The desktop has ONLY BIOS, no UEFI at all. The boot drive can only be MBR in that situation, even though the CPU and the OS are both 64-bit. And yet I have had no real trouble installing the 17xxx build on this desktop, repeatedly. I have had the same problems a lot of people are having inside the build, particularly 17046 (and some minor issues even in 17063), but no major install issues.
So, that kinda kills your theory.
In addition, kind of supporting your theory, but now really, if you read the entire thread, is this thread where we are working to get Bordi onto a 17xxx build, which his machine refuses to - Win 10 RS-4 not compatible with Intel DX58SO motherboard - Windows 10 Forums
Now, if you read that thread, though he is using a different motherboard, an Intel, it has the same main chipsets on it as mine, namely the X58, the ICH10R, and even another controller chipset made by Marvell. He had been trying everything but upgrades from 16299, aka FCU, continue to fail for him. His theory is similar to yours, but it is even more poignant in that his motherboard hardware is so similar to mine, whereas mine works and his does not.
I can understand why you would think that your recent experiences would lead you to believe you have the answer, but my machine stands in the way of supporting both your and his theories as to why this is occurring. My CPU is almost 9 years old, my motherboard is 7, and it has no UEFI onboard anywhere - it is strictly BIOS based, as I mentioned above. And it is still running 17xxx builds, so that, in and of itself, is counterintuitive to your supposition.
I hope my logic-based response is not antagonistic, as I am not trying to antagonize you at all, merely stating facts. However, in point of fact, your supposition is incorrect, because of it were true, me and MANY other users would also have these problems that you do.
One thing to consider, though - it could be Acronis itself that is causing you installation problems with this build, something to consider.
My sister, finishing her Ph. D. in Pharmaceutical Science, was in Hawai'i for 6 years, and I had to remote support her machine from mainland US. She, too, had an older version of Acronis that she used religiously to make full backups of her system nightly and weekly (the scheme was actually differential for the week and full for the weekend, but not really important here). I believe it was Acronis 2013, not sure, though,my might have been a slightly older, back to 2011. But while working on her Ph. D. she had to use a lot of legacy hardware in the labs, so she remained on Windows 7.
Last year, as she began the final stages of defending her dissertation, once she was done with her lab work, she decided to upgrade to Windows 10 - and Acronis immediately started having massive issues - backups not run, error messages about drives not found when they were connected, etc. They got so bad that 1 year ago, about 4 months after her Windows upgrade, I spent the better part of 5 days working on her machine and researching other options for her, and migrated her to Macrium free.
I had bought her that license of Acronis, a family pack, no less, so it feels like I am taking a hit in my wallet. But in reality, it is Acronis who is taking the hit because I will never again recommend their product for use because of the absolute lackluster responses from them, which always amount to ”But this problem doesn't exist in any of our newer products!”
Macrium free works perfectly, using all of the same type of options and with a very similar setup as I had her running in Acronis - and now she has 0 errors and is happily working on her final revisions.
So, the choice is yours, but I will leave you with this final thought:
Your version of Acronis was developed around the same time as my CPU was made. 9 years is a long, long time in terms of software development. If you really want to continue using Acronis 2009, you should really consider not using anymore Insider Preview builds, after all, I am almost positive that Acronis offers 0 support for Windows 10 in that 2009 version.
Even if it does everything you want exactly how you want, your OS has grown by leaps and bounds, and you should consider replacing legacy software with current, nature software that is designed to work with modern OSs.
At any rate,, good luck with your issues, if you want to start another thread like Bordi did to try to work through this, I will offer whatever assistance I can there as well.
Good luck.
Quote