![]() So for anyone who has the option of rolling back to an older desktop image (pre 2014-12 would be a good bet), at least you still have that as a possibility in order to create a working PE image. I kept it offline to leave it at that old patch level and reinstalled all the current AOMEI stuff and once again was able to generate a properly working PE image. I was able to find a VERY old ghost image that I restored to the laptop after that, from 2013-12. That was almost 20 boot images and took quite some time. This means I uninstalled ONE fix at a time, and created brand new PE USB keys in between each uninstallation of a hotfix. Unfortunately, by the time I tried uninstalling the 20th or so fix from my list of ~30 something hotfixes, it resulted in a really unstable system and I still hadn't gotten a working PE out of it. Trailing off, I tried to do a bit of public service to see if I could narrow down exactly which fix (or fixes) specifically seem to break PEBuilder. and makes whatever (older) versions that come pre-bundled with PEBuilder a little irrelevant. ![]() To be fair, since the PE created on currently patched (post 2014-12) WinOS fails to boot, it hadn't occurred to me that if the newer versions of Backupper and PA are installed before creating the PE, then those updated versions get copied into the PE. it's a portable but FULL running version of Windows (not a PE), so any tools any of us might have wanted to add to the PE image but couldn't get to work because of missing system dependencies won't have that problem under Win2Go.īut seeing almost half a year go by without a SINGLE comment from AOMEI about this show-stopping bug that I troubleshot for them has convinced me this is not a company to spend money with. ![]() I think I'm ready to give up on a PE environment based approach alltogether, and instead try working in a Win10 Windows 2 Go environment. Does this mean that AOEMI didn't do ANY QA testing on PEBuilder 1.5 at all? Or does it mean that they are inexplicably testing their new software releases only on OLD versions of Windows?īeyond that - it ALSO looks like PEB 1.5 includes OLDER versions of BOTH backupper and partition assistant than the versions that came bundled in PEB 1.4? Whaaaaaat? In other words, it seems as though the problem should happen to ANY and EVERY person with a fully patched Win7 圆4 system. The hotfix compatability problem I reported here that causes the BSOD doesn't appear to be an issue that is specific to hardware. I have to say - I just don't understand what the point of releasing 1.5 was. I actually went back to compare the last "working" WIM image that I built with PEBuilder 1.4 to the latest non-working WIM image I just built with PEBuilder 1.5.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |