New
#10
Just subscribed to the release preview ring and downloading (KB4512941) right now.
- - - Updated - - -
Follow-up on my post # 11:
-Subscription to this IP Release Preview was successful:
-Better yet, my File Explorer's search bar is still there comparing to when I was on Fast ring. This was the main reason, I left the latter, let alone the instability I was also experiencing with the cursor. I understand that the IP is made to help MS in fixing bugs, but in my case, the aforementioned bugs were fixed for everybody else, but me.
On the other hand, there are bugs (acceptable and MS let you know about them and trying to find a fix) and bugs that can render your machine unusable (those are very difficult to swallow, figuratively speaking) .
I discovered that the screen won't remain turned off /black after locking the computer (with WIN+L for instance).
Normally when locking, the sync output is turned off within a minute or so and the monitor goes to sleep. Now my screen wakes up and show the login prompt after a couple of minutes, turns off again and wakes up again after further couple of minutes in an endless loop.
Same behaviour on two different physical computers (no virtual machines involved). Anyone else seen this?
Cortana is sitting at 0% cpu use for me.
I also had the same issue, the "AllowCortana" and "BingSearchEnabled" registry settings needs to be set to 1 to fix the issue.
Code:Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search] "AllowCortana"=dword:00000001 "BingSearchEnabled"=dword:00000001
By instability, I meant while I was still on IP Build 18936 or the one previous to that, not only the File Explorer's search bar was a no-show, but the cursor was kind of bumpy in action and wouldn't stay where I put it. That was intermittent, but frustrating enough to cause me to roll back. On that machine right now, I am on 1903 IP Release Preview. Everything is working fine so far.
I could never find the cause or reason behind this behavior. That was on my second machine (specs in my profile) a clunker but still alive and working well with Logitech M510. On my main machine, using a MX Master (Logitech), I had a similar problem on 1903, and also rolled back to 1809 where I stand right now and won't upgrade to 1903 until 19H2 is out in a couple of month or so..
- - - Updated - - -
I have noticed the same behaviour after installing this Build, but I did run the routine DISM.exe command-lines plus sfc /scannow. The latter seemed to have found some corrupt files and repaired them. For now, I am experiencing some stability, and I don't notice the issue anymore (fingers crossed).