2015-10-07, 03:37
Am about to uninstall and do another reinstall of Kodi.
My experience personally is that just yesterday I clean installed Win 10 Pro with a purchased retail key on a 2015 AlienWare 17R2.....after my clean install of 10 I did install program after program after program - I use a lot of different software and I am wondering if maybe somewhere along the line I should have given it a break and done some shutdowns and restarts or something (maybe my machine itself or Win 10 got confused
Anyways....will try again and make sure I get rid of all Kodi remnants using Revo but if that fails I may just clean install Win 10 again and test Kodi (with how I setup including OzWeather) prior to pounding the machine with x amount of other program installations.
From reading around the place I think there may well be bigger issues at hand with Kodi and Windows 10 though unfortunately. I am personally witnessing some very weird behavior and only hope I can get this all happening again. ....(possibly because Win 10 is using Direct X 12)
I'll let you know how I go - if the error persists should I happen to start from scratch again with the whole lot I will look at creating another log to post.
Thanks for the reply @boss
My experience personally is that just yesterday I clean installed Win 10 Pro with a purchased retail key on a 2015 AlienWare 17R2.....after my clean install of 10 I did install program after program after program - I use a lot of different software and I am wondering if maybe somewhere along the line I should have given it a break and done some shutdowns and restarts or something (maybe my machine itself or Win 10 got confused
Anyways....will try again and make sure I get rid of all Kodi remnants using Revo but if that fails I may just clean install Win 10 again and test Kodi (with how I setup including OzWeather) prior to pounding the machine with x amount of other program installations.
From reading around the place I think there may well be bigger issues at hand with Kodi and Windows 10 though unfortunately. I am personally witnessing some very weird behavior and only hope I can get this all happening again. ....(possibly because Win 10 is using Direct X 12)
I'll let you know how I go - if the error persists should I happen to start from scratch again with the whole lot I will look at creating another log to post.
Thanks for the reply @boss