Bork Tuesday, Any Problems Yet?

I am noticing a pronounced black screen prior to desktop initialization after the latest 1909 cum. update. Unlike previously where this occurred after update and improved w/each subsequent reboot, the reverse is happening. Each subsequent system startup is taking longer to initialize the desktop.

 

Is it to where you'd consider uninstalling this update and then blocking it? It does seem to trigger somewhat more complaints than the one just previous to this. There's a (now) three-page long thread on it in the Microsoft forums.

 

Also, I think I'm a little late with this realization that apparently, you can't clean Windows Update files from the deprecated Disk Cleanup app any more, it's only available via Settings/Storage, it seems. I got back 3.9 GB of disk space that otherwise would have sat there.

 

not true. you can do it. you need to run dc as administrator via context menu or under an administrator acc.

 

I was experiencing the same thing, just without the black screen you mention. It turns out after checking my SRP advanced logs, the policy was blocking several MS files in mostly Temp folders. Some of the new updates were obviously creating files not yet included in SRP's Unrestricted Path rules. After creating Path rules for them and rebooting, things are much better now. My policy is based on very restrictive Path rules, so this affords stronger security at the cost unencumbered usability.

BTW, I hardly ever use Windows any more. Only on rare occasion to patch the O/S and update other programs.

 

No SRP applied here. Culprit might be Eset startup scanning activities.

 

Yep, I do this routinely--as administrator. I didn't see the update cleanup the last time I updated. Maybe I missed it, it's not at the top of the list any more. Anyway, it would be nice if it was one or the other, not both. Build is 18363.628.

 

Perhaps you are not familiar with this as you think you are.

Even when you run your computer as an Administrator (as I do, Local Administrator account), for the option to clean up Windows updates to show up in Disk cleanup, you have to run Disk cleanup as Administrator via context menu.

FWIW. I always cleanup Via Settings, it does a great job. In W10, I used DC only the first couple of times I cleaned Windows updates, after that, I started doing it in Settings. You can also cleanup the Windows.old folder via settings. Cleaning up via Settings does a very smooth job.

Bo

 

yeah, i got the same build and it was there last time i ran it (couple of days ago).

 

no, elam. i am.

 

Windows search is no longer working today.I have the optional update installed that was supposed to fix it on 1909.It could have been borked by a Windows Defender Update.It worked fine until today.

 

I don't know that it's a bork Tuesday issue or not but the start menu search is not working on any PC in the office this morning. I'm sure they have broken something.

 

Probably not a Defender issue. I am running 3rd party AV on 1 PC and it is also on the Slow Ring of the Insider program. This is likely a server side issue.

 

Confirmed! You can type in the box, hit Enter and nothing happens. The whole field is entirely blank.

 

Yes blank.Go to bed,wake up,and borked! Looks like where waiting it out.

 

No problems here either today or previously regardless of latest optional update.

I have always had cloud search disabled. I don't use Windows Defender; disabled via third party AV install.

 

Search is down for Windows 10 users
February 5, 2020
https://betanews.com/2020/02/05/search-down-windows-10/

 

Running a manual defrag solved this. The strange part is a scheduled defrag ran on 1/31 and did not fix it.

 

If you want to disable Bing from the search menu it will fix it. Paste into reg file and import.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search]
"CortanaConsent"=dword:00000000
"BingSearchEnabled"=dword:00000000

--Ok, it worked on the 1909 builds. Still not working on the 2004 version.

 

Let MS fix it because I'm sick of fixing their screw ups.

 

Search is working fine here.