Thanks i'm looking at this.Virs wrote:16.0.0.2 gave me back the error, so here are logs after 16.0.0.1 and another after 16.0.0.2.
http://www.mediafire.com/download/xv87m ... U+Logs.rar
I'll send you two registry exports by PM. The "Before" reg is after I used 16.0.0.1, but before 16.0.0.2.
The "after" log is after 16.0.0.2.
I wonder if its not the AMD uninstaller that may break things up too.Virs wrote:I want to add its possible the issue appeared with 16.0.0.1 and I didn't realize it at first. The reason I say this:
After using 16.0.0.1 I used the AMD installer from 16.6.1 (bugged because of AMD I think) and then 16.5.3, which worked fine. So I figured the issue didn't appear.
But before using 16.0.0.2, I uninstalled the AMD package with their uninstaller. Everything was removed, but it told me it hadn't uninstalled successfully. This is despite their log saying "success" to everything.
Then after I used 16.0.0.2 and saw the issue was back again.
I had created my own system restore before even using the AMD uninstaller and restored my system back to that point. I uninstalled the AMD drivers with the uninstaller and then tried installing them normally again, without using DDU this time around. I still get the "installation failed" message. So it's possible 16.0.0.1 brought back the error, but it didn't show itself on the very first installation. I'm not sure.
Try to install directly from c:\amd (or where the AMD package is extracted) I heard someone that told me it failed with the downloaded web EXE but it was working with the extracted files in c:\AMD.Virs wrote:I tried going back to the system restore after using 16.0.0.1, it's the earlier I got since W10 somehow deleted my system restores. It seems to be doing that randomly. (Despite having enough time)
I tried uninstalling with only the AMD Uninstaller and the issue still appeared, but that was after 16.0.0.1 so I can't be sure.
And the "after" registry export was after using 16.0.0.2 and having tried to install the driver, but the driver didn't install. (The rest of the package did, but not the actual drivers).
If you reinstall, keep me posted.Virs wrote:I usually install from C:/AMD, I switched to AMD2 just to test it out. I have a folder in AMD that I cannot delete (WU-CCC2) and wanted to see if switching to a new folder would help.
The issue could be because of Win10 insider (I believe the issue with 16.6.1 is because of this, not DDU), but I've had it without Insider builds. I was on the normal version of Windows 10 when it originally released, and I already had this issue back then. I've had it for a very long time, the first time I asked for help I didn't realize it was possibly/likely related to DDU, so I didn't get much help and then I found out I could install drivers manually, so I kinda just lived with it.
Since my Windows 10 Insider is a bit buggy, I might do a clean install to the build I'm currently using (instead of upgrading to new builds) and see if it's more stable, and if it helps with the drivers.
At least we know now that a fresh build 14342 isnt an issue.Virs wrote:I delete my previous Windows partitions and did a clean install of the same Insider build I was using before (14342).
So while before I used a vanilla version of Win10 and upgraded through the various Insider builds up to 14342, this time I installed with 14342 as the base.
Installing 16.6.1 worked fine, I didn't get any issue this time around. Since other people have reported suffering from the same problem with 16.6.1 (on guru3d forums and AMD subreddit) it might be worth seeing if the issue comes from Win10 Insider builds, or from using DDU like I did.
I'll keep a look on the log files if I use DDU for future drivers. I don't know if reg export would be useful to you since I haven't used DDU at all on this installation, but I can send some to you if you want to compare, with a Windows installation that is working normally.
