I think Microsoft changes stuff around just to change it. :)
I just returned my machine to a dual boot status a few days ago; my Insider partitions was named Insider and my other partition was named Windows 10 RTM. This morning, however, Insider had been changed to Windows 10! Go figure!
There are tons of complaints about BT in the hub, and on the forums. So, no. I don't think it is just on my end. Besides that, I have an extremely powerful sys that I built myself. I've gone through everything, and have zero problems with any of my hardware, and all other software runs quick and smoothly. I also dual boot booted a Win 7 OS, and BT works perfectly well on it. Lastly, M$ has a history of horrible BT interphases and I have rarely seen them put a concerted effort into doing anything about it.
Thanks Wynona. I don't take it personally. Although I'm not sure the purpose of his post.
I updated all apps before upgrading. A number of apps were not updated and were date stamped 11/03/18.
When I upgraded, when I checked for updates, it said I was fully upto date. Those date stamped 11/03 were identical to earlier build. The rest had different build numbers, so the new build does pick up later versions but I cannot tell if that was built into the upgrade files, or if the upgrade downloaded them on the fly.
Of course, this is moot, and I am wondering if the difference is 17120 is skip ahead versions (where different) become the start point for 17120 - I will need to check further but no doubt some apps are newer on 17120 compared with 17115.
Yeah, I have a BT keyboard that I love, and a wireless keyboard that I hate. And these days I am forced to use the wireless keyboard, because the BT keyboard will not stay connected. And it's just too much of a pain to continually go through the connection process. So at the moment, the BT keyboard is useless.
Networking drivers have been a pain for me for months, even when i go to advanced and select 5g only it still connects on 2.4????
Roy
Updated to 17120 last night in about an hour including the ISO creation. I also installed FF 59.0 and FF 60.b3 and both ran as before. Did have some difficulty loading a few pet non-ms apps for the first time as an insider, but that was solved after a reboot. All in all it is working fine. It seems like it is close to RTM.
WEK
Audio service not running.
17115 was had no problem, so what is this bug?
We need a quick patch asap.
Faulting application name: svchost.exe_Audiosrv, version: 10.0.17120.1, time stamp: 0xa38b9ab2
Faulting module name: KERNELBASE.dll, version: 10.0.17120.1, time stamp: 0x63c6c395
Exception code: 0xc00000fd
Fault offset: 0x0000000000045730
Faulting process ID: 0x2ad0
Faulting application start time: 0x01d3bbbc287629a4
Faulting application path: C:\WINDOWS\System32\svchost.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 87e25cd2-576e-4743-944a-257cfb833586
Faulting package full name:
Faulting package-relative application ID:
Last edited by GunnzAkimbo; 14 Mar 2018 at 13:15.
Installed it fine from build 17115.1,no watermark or time bomb,this could be RTM candidate.
LE Forget about watermark and time bomb,it appear after second restart.
Quote