I used to have Taskbar disappearing bug in older Insider builds while using Firefox. I used Nvidia GTX 970. Then I upgraded to GTX 1070 and used the latest drivers released few days ago and also updated to 14393. Now I don't get that bug. Something fixed it and hard to pinpoint if it were drivers or hardware. If you are getting the same bug, Fresh install 14393 and download the latest Nvidia drivers. I am using Firefox 47.1 (Latest official Non-beta)
Yeah, i have the latest drivers, tried installing the normal mode (over previous ones checking the "correct install" option), tried removing the previous one with DDU, tried installing just graphic, audio and physX drivers (no 3d vision or GFE), no change, so as you suggest and i said before, my last chance is to test after a clean install, at least for discard all variables on my system. Already reported to nvidia and the video that i recorded is an nvidia team request because with just my text as instructions they've been unable reproduce the bug, so now i must wait to know if they can reproduce with the video as guide.
This is one of worst os that has rolled out 1511 works better than this duel boot win 8.1 and this s**t and go though checkdisk hell or lock up or amd drivers 16-7-2 will not install driver not sign
i have 16.7.2 installed and working 100% use ddu from guru3d.com and try again user error is not a bug or os related issue
14393 works really for me, if you want to know... No chkdsk problems, no lockups, etc, of any kind and everything runs really well atm. The 16.7.2 driver is signed, it's just that apparently the current builds of Win10x64 are having a difficult time with AMD's SHA-256 signed driver certificates (SHA-1 certificates--all the Crimson releases starting with 16.5.3 and earlier--are SHA-1 signed certificates and they all work fine with Win10x64--16.5.3 works great with 14393, secure-boot on.) 16.7.2 actually installs and runs fine with 14393 with one caveat: you have to turn secure-boot OFF. It's all because of an incompatibility between AMD's SHA-256 signed certificates and Microsoft's latest Windows 10x64 code. Whose precise "fault" it is is unknown at the moment--I hope they can reconcile it before the final public build is released in a couple of weeks.
what? yes they do you cant turn off insider preview unless you install a non preview build. its been like that forever even if it was rtm he would still have to reinstall the release version to stop downloading preview builds
If I understand correctly If we wanted to install the RTM and stop insider updates there's no point in installing this release even if it is the RTM ?
No. The only difference between insider and non-insider is whether you've opted into the insider program. The build is absolutely the same. I've tested the contents when 10586 came out. The registry files had the exact same hashes.
It's not the files signed with their SHA256 certificate that cause issues, the certificate is flagged as valid. It's the files signed with their "AMD PMP-PE CB Code Signer v20160415" self-signed SHA1 certificate that cause issue because the certificate is flagged as invalid in the latest rs1 builds. 16.7.2 even doesn't load if I manually install the drivers. The latest driver that seem to be working is the 16.6.2, and only if you manually install the driver using the Device Manager.
I noticed that quitting insiders right after 10240 "rtm" was released in the fast ring I had a reboot that got rid of insiders gui, it kept 10240. I guess it would be the same same now