Two major bugs continue to dog Win10 version 1909 — A mysterious persistent wake-up call, and the ubiquitous File Explorer Search bugs

Topic

New Reply

Microsoft said the 1909 upgrade would be easy — a “master switch” change to an already altered Win10 version 1903. It didn’t work out that way. I see
[See the full post at: Two major bugs continue to dog Win10 version 1909 — A mysterious persistent wake-up call, and the ubiquitous File Explorer Search bugs]

2 users thanked author for this post.

lmacri, GreatAndPowerfulTech

Reply | Quote

Replies

[GreatAndPowerfulTech]

I have 1909 on my laptop. Since I installed it, Flash resets itself to allow the camera and mic to be used remotely with each cumulative update. This is terribly annoying. The Flash settings were stable for years. Now, it’s back to the same old seemingly random changes in W10. Also,on a side note, I forgot to remove my SD card before the November cumulative update (My laptop had 1909 installed from the Insider program, which I now intend to avoid in the future). Lo and behold, all the data was wiped, again. Sigh. I haven’t had to battle with an OS this much since Windows 3.1.

Edit: The change to my Flash settings in Control Panel happen now with each reboot. Thanks again MS.

GreatAndPowerfulTech

• This reply was modified 5 years, 3 months ago by GreatAndPowerfulTech.

Reply | Quote

There has to be more to this.  I just tried setting Flash Player to block all sites from using the camera and microphone, then rebooting.  The setting persisted.

 

Reply | Quote

warrenrumak: The flash settings persisted since Windows 10 came out. Only with v.1909 am I having trouble with it changing back to the default setting. The spontaneous bugs of Windows 10 are many. I own a small computer shop and am no longer surprised at the nonsense that happens with Windows 10. I like how it works, when it works properly.

GreatAndPowerfulTech

Reply | Quote

I normally have Windows Search disabled in Services.  I enabled it to check the parameters listed in your ComputerWorld article, but it works as it should.  I can paste from Notepad into the Search Box, the search commences and runs to completion.  I can only surmise that Search works as it should for me, but I choose not to use it.

As for ‘NT Task\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start’ task in Task Scheduler, I don’t have it.  It does, however, appear in the registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Ubpm]
“CriticalAction_MsCtfMonitorTask”=”{01575cfe-9a55-4003-a5e1-f38d1ebdcbe1}”
“CriticalAction_NGenTask32″=”{de434264-8fe9-4c0b-a83b-89ebeebff78e}”
“CriticalAction_NGenTask64″=”{613fba38-a3df-4ab8-9674-5604984a299a}”
“CriticalAction_SystemSoundsService”=”{2DEA658F-54C1-4227-AF9B-260AB5FC3543}”
“CriticalAction_WinInetCacheTask”=”{0358b920-0ac7-461f-98f4-58e32cd89148}”
“CriticalMaintenance_appuriverifierdaily”=”NT Task\\Microsoft\\Windows\\ApplicationData\\appuriverifierdaily”
“CriticalMaintenance_BgTaskRegistration”=”NT Task\\Microsoft\\Windows\\BrokerInfrastructure\\BgTaskRegistrationMaintenanceTask”
“CriticalMaintenance_DefenderCleanup”=”NT Task\\Microsoft\\Windows\\Windows Defender\\Windows Defender Cleanup”
“CriticalMaintenance_DefenderVerification”=”NT Task\\Microsoft\\Windows\\Windows Defender\\Windows Defender Verification”
“CriticalMaintenance_SetupCleanupTask”=”NT Task\\Microsoft\\Windows\\Setup\\SetupCleanupTask”
“CriticalMaintenance_SilentCleanup”=”NT Task\\Microsoft\\Windows\\DiskCleanup\\SilentCleanup”
“CriticalMaintenance_UsoMaintenanceInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Maintenance Install”
“CriticalMeasured_UnivOrch”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Universal Orchestrator Start”
“CriticalMeasured_UnivOrchIdle”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Universal Orchestrator Idle Start”
“CriticalMeasured_UsoAcPowerDownload”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\AC Power Download”
“CriticalMeasured_UsoAcPowerInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\AC Power Install”
“CriticalMeasured_UsoBrokerDisplay”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\USO_Broker_Display”
“CriticalMeasured_UsoCombinedInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Combined Scan Download Install”
“CriticalMeasured_UsoPolicyInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Policy Install”
“CriticalMeasured_UsoReboot”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot”
“CriticalMeasured_UsoScheduleRetryScan”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Retry Scan”
“CriticalMeasured_UsoScheduleScan”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan”
“CriticalMeasured_UsoScheduleUpdate”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Update”
“CriticalMeasured_UsoScheduleUpdateBackup”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Update Backup”
“CriticalMeasured_UsoStaticScan”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan Static Task”
“CriticalTask_CellularProvisioning”=”NT TASK\\Microsoft\\Windows\\Management\\Provisioning\\Cellular”
“CriticalTask_DM”=”NT TASK\\Microsoft\\Windows\\EnterpriseMgmt\\*”
“CriticalTask_FamilySafetyRefreshTask”=”NT TASK\\Microsoft\\Windows\\Shell\\FamilySafetyRefreshTask”
“CriticalTask_NlaWiFiTask”=”NT TASK\\Microsoft\\Windows\\NlaSvc\\WiFiTask”
“CriticalTask_ShellCreateObjectTask”=”NT TASK\\Microsoft\\Windows\\Shell\\CreateObjectTask”
“CriticalTask_UnivOrch”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Universal Orchestrator Start”
“CriticalTask_UnivOrchIdle”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Universal Orchestrator Idle Start”
“CriticalTask_US03″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan Static Task”
“CriticalTask_US04″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Backup Scan”
“CriticalTask_USO1″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan”
“CriticalTask_USO2″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Battery Level Install”
“CriticalTask_UsoCombinedInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Combined Scan Download Install”
“CriticalTask_UsoEnableUWF”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Enable UWF”
“CriticalTask_UsoReboot”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot”
“CriticalTask_UsoScheduleUpdate”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Update”
“CriticalTask_USOUXBROKER1″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\USO_UxBroker”
“CriticalTask_USOUXBROKERRebootAC”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot_AC”
“CriticalTask_USOUXBROKERRebootBattery”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot_Battery”
“CriticalTask_USOUXBROKERRebootWCOS”=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot”
“CriticalTask_WiFiTask”=”NT TASK\\Microsoft\\Windows\\WCM\\WiFiTask”
“CriticalTask_WUScheduledStart”=”NT TASK\\Microsoft\\Windows\\WindowsUpdate\\Scheduled Start”
“CriticalTask_WwanWiFiTask”=”NT TASK\\Microsoft\\Windows\\WwanSvc\\WiFiTask”
“CriticalTask_XblGameSaveTask”=”NT TASK\\Microsoft\\XblGameSave\\XblGameSaveTask”
“CriticalTask_XblGameSaveTaskLogon”=”NT TASK\\Microsoft\\XblGameSave\\XblGameSaveTaskLogon”
“OOBETask_AikCertEnroll”=”NT TASK\\Microsoft\\Windows\\CertificateServicesClient\\AikCertEnrollTask”
“OOBETask_CellularProvisioning”=”NT TASK\\Microsoft\\Windows\\Management\\Provisioning\\Cellular”
“OOBETask_DM”=”NT TASK\\Microsoft\\Windows\\EnterpriseMgmt\\*”
“OOBETask_MsCtfMonitor”=”NT TASK\\Microsoft\\Windows\\TextServicesFramework\\MsCtfMonitor”
“OOBETask_NgcKeyPreGen”=”NT TASK\\Microsoft\\Windows\\CertificateServicesClient\\KeyPreGenTask”
“OOBETask_StoreLicenseMigration”=”NT TASK\\Microsoft\\Windows\\Clip\\License Validation”
“OOBETask_TpmMaintenance”=”NT TASK\\Microsoft\\Windows\\Tpm\\Tpm-Maintenance”
“OOBETask_US03″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan Static Task”
“OOBETask_USO1″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Scan”
“OOBETask_UsoPolicyInstall”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Policy Install”
“OOBETask_UsoScheduleUpdate”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Update”
“OOBETask_UsoScheduleUpdateBackup”=”NT Task\\Microsoft\\Windows\\UpdateOrchestrator\\Schedule Update Backup”
“OOBETask_USOUX01″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\Reboot”
“OOBETask_USOUX02″=”NT TASK\\Microsoft\\Windows\\UpdateOrchestrator\\USO_UxBroker”

On the other hand, I neither Sleep nor Hibernate my PC, so it wouldn’t be an issue, anyway.  My installation of 1909 doesn’t seem to have any dogs in it that I can whistle up.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren wrote:

I can paste from Notepad into the Search Box, the search commences and runs to completion.

Via a mouse right-click?

Reply | Quote

b wrote:

Via a mouse right-click?

I used my habitual Ctrl + V to paste.  I just re-tried with a right-click, and that failed.  I guess I have a puppy, after all, but one that doesn’t get underfoot.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

woody, b

Reply | Quote

The almost impossible to turn off, wake up the computer once a day bug exists in Windows 1903. (Actually, in my Google searches, I’ve seen people complaining about the UpdateOrchestrator service/scheduled tasks all the way back to Windows 1709.) It affected me for weeks, except my computer was turning on at about 12:05 AM every day. What was really making me mad was my computer was still waking up after I used the “Shutdown” option to turn it off, not just the “Sleep” or “Hibernate” options. My initial work around was just to unplug the computer every night after using the “Shutdown” option, which was annoying.

I did finally find a website that told me how to “fix” the problem, which has worked for me since I did it (sometime in November). Unfortunately, I’m at work, not at home, and I don’t remember all the details and I’m not finding the website I used. What I do remember is I had to go into the folder where the scheduled tasks live, take ownership of the two UpdateOrchestrator tasks that were the problem (they have “reboot” in the file name), rename them so they have an extension (I think I used .BAD), and finally create an empty folder called Reboot. There may be other steps that I’m not remembering.

So far, this has survived through the automatic, daily Windows update checks and me checking for updates via PowerShell. In other words, I’m using the “Sleep” option to “turn off” my computer every night and it is no longer waking up by itself at 12:05 AM. I can’t remember if I did this before or after installing November’s cumulative updates. I have not yet installed December’s updates. It’s my understanding that if I run the sfc program, this will get undone. I’m not sure if it will survive the checks you can do with the dism command. There are likely other scenarios that will undo this “fix”, but, as I said, it’s working for now.

2 users thanked author for this post.

woody, b

Reply | Quote

Interesting question on Twitter from Bryan Dam:

Does it matter how they got to 1909 or do both methods lead to the issues you’re talking about?

Reply | Quote

To followup on the UpdateOrchestrator issue, I didn’t have the problem prior to 1903 nor when I first went to it (not long after it was released). Something changed in the September/October time frame that caused this to start. I have no idea what the change was, although the easy guess is one of the monthly updates. But, that begs the question of what’s different enough about my system to cause the bug to bite me? I don’t know.

I run Windows 10 Professional. I do have some non standard settings in place. I have group policy settings to defer quality updates for 15 days, to defer feature updates for 90 days, and to not retrieve drivers from Windows Update. I also have a group policy setting so that Windows Update tells me when updates are ready to be downloaded. They’re not automatically downloaded and installed. I have my active hours set to something like 6:00 AM to 10:00 PM. In the BIOS, I have wake events set to be controlled by the OS. I don’t know if any of this matters.

Reply | Quote

An uncanny ability, on some machines, to wake itself up every day

Is this new to Windows 10 1909? On older versions I used to have to run some powershell to change scheduled tasks as TrustedInstaller (!?) to fix this. Haven’t run into this on 1909 so far, but I’ve also went and disabled every possible setting related to wake timers in the bios before then, so that may be why I didn’t get a re-occurrence.

The long-documented File Explorer Search bugs

I hardly ever use the file explorer search bar, but one of the rare times I did I ran into the inability to focus even with a left click. The new search bar also looks sloppy and inconsistent with the navigation bar. When you click it for the first time, the cursor appears to pause for a second before blinking in a way that is inconsistent with other text entry boxes on Windows.

Another irritating bug in explorer I’ve noticed: If you use “Launch folder window in a separate process” on a system with a scaling factor > 1, text in explorer will be blurry.  Probably not immediately after enabling the setting, but after a reboot. Not sure if this one is new though. This is a handy setting for improving system stability (a temporary lock up in explorer caused by waking up an external hard drive should NOT lock up your shell), and should really be enabled by default in 2019, but maybe MS hasn’t enabled it by default because they know it’s buggy.

Reply | Quote

“Wake the computer spontaneously” bugs tend to burn up computers stuffed in bags. And we know who’ll sell you a new one.

Be careful.

-Noel

Reply | Quote

This literally happened to a client of mine earlier this year.  Fairly expensive CAD capable laptop too.  It was enough to make me want to disable hibernate AND sleep for him.

~ Group "Weekend" ~

Reply | Quote

In Device Manager, check that no device has a tick against “Allow this device to wake the computer”.  Usual culprits are keyboards, mice and network adapters,but there could be others, and the setting may have changes with 1909.  Right-click the device, then Properties, then Power Management.

I use Hibernate when I have finished with the computer, and once it has finished and the disk access light has gone dark, I then turn everything off at the wall (computer, printer, router etc.), all via a single switch.  This means nothing at all could happen overnight, because there is no power, everything is OFF (desktop, AC only, no battery).   When I want to use the computer again, I just turn that switch back on, then press the power-on button on the front of the case, and wait a few seconds for the computer to wake from hibernation.  Works every time, and the advantage is that while the switch is off no power is being consumed, and no one can access the router (not that they could anyway).

I’m using 1903, and the problem referred to above (“The almost impossible to turn off, wake up the computer once a day bug exists in Windows 1903″) has never happened to me.

Windows 10 Pro 64 bit 20H2

Reply | Quote

Inline but off topic?….Woody, thanks for the Christmas Carol illustration! Wife’s an artist…we love it, thanks for sharing!

Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

1 user thanked author for this post.

woody

Reply | Quote

Anyone else having problems with Win 10 Pro 1909 x64’s Start > Power > Shut down and Start > Power > Restart not doing a flipping thing?

I’ve clean installed several times on a Dell Latitude E7450 laptop and it’s reproducible.

Sometimes it works… sometimes the commands are just ignored.

1 user thanked author for this post.

woody

Reply | Quote

Folks administering Win 10 machines who want to maintain maximum control of upgrading (and possibly also avoid the repetitive auto-wake issue described above), in favor of controlled manual or third party Window Update Manager utility,  will want to disable or delete all scheduled tasks associated with Customer Experience, Update Orchestrator, WAAS Medic, and Windows Update services.  Methods for this have been posed on Ask Woody and other sites.  To ensure Win Defender signature updates, create a 3 times per day batch file run of the command line to update signatures.

Reply | Quote

I recently had a W7 re-blown to W10 Pro.
Customizing it to my ‘specs’; it updated to ‘1909’
HP Printer Bug appeared. Changed the printer driver.
What’s wrong with W10: MS keep reissuing it, far too often.
Not being an ‘entomologist’. and my hard-disk, not being an ‘insectarium’.
WHY ALL THE BUGS ?

Reply | Quote

Yep. HP printers are so much easier on platforms other than Windows 10. 🙄

E.G. 150 posts and still not working: HP all-in-one printer in Mint

Reply | Quote

I’ve become aware that I have the insomniac bug and I’m pretty certain it’s a new development for me. The PC started waking itself constantly last night and I finally just turned it off so I could get some [EDITED] sleep.

It was not doing this before last night. The only thing I can think of that’s changed is I have disabled “Fast Startup” and “Hibernate” to try to see if that would solve a different issue (my AMD graphics driver settings keep resetting on reboot).

I read someone’s Reddit post where they say disabling “Wake Timers” in advanced power settings will fix this issue. I’ll try that for a few days and see if it works.

In my case, this is a brand new PC, brand new copy of Win 10 Pro 1909 installed less than a month ago. I have Windows  Updates set to check and notify, but not download or install (via group policy). I’m using a local account, which was briefly hijacked into a Microsoft account when I logged into the Windows Store, and then converted right back to a local account (I’d like to strangle whoever designed it to do that).

I see I also have that search bug, but I didn’t notice it until now because I never use File Explorer’s search anyway. I use a search tool called “Everything” when I need to search for a file. It’s amazingly fast and finds whatever I’m looking for before I even finish typing the name.

EDIT: for language (again)
“Swearing, cursing or blasphemy are unacceptable” (from Lounge Rules – please familiarise yourself with them)

Reply | Quote

So, a few days later and this problem hasn’t come back. Go to Settings > Power and sleep settings > Additional power settings > Choose what power buttons do > Change plan settings > Change advanced power settings and FINALLY the dialog you want pops up (goodness, Microsoft). Change to the power profile you’re using in the drop down, go down to +Sleep > +Allow wake timers and set it to disable.

I tried the method posted elsewhere using psexec to launch the task scheduler, but the entries for reboot were already set to disabled. I did find 10 entries there, two of which were set to “wake the computer .” I’ve disabled that and reenabled wake timers to see if the problem comes back. I have automated backups and would rather have the software be able to wake the computer to run, so keeping “wake timers” disabled permanently isn’t a good option for me.

1 user thanked author for this post.

DriftyDonN

Reply | Quote

This was posted in may 2018 on https://answers.microsoft.com/en-us/windows/forum/windows_10-update/disable-update-orchestrator-from-waking-my/19272430-f41f-4947-904c-71ab34b220f0

Im using ver1903 pro. The updateorchestrator section has 11 triggers, not just one!! The end result is feedback hub and you dont even have to sign in. FYI<It doesn’t work yet either!!

First go here to download PsTools. Extract it to a folder on your desktop.

Open Start and type cmd. Right-click the program and choose to run as administrator.
Navigate to the folder where you extracted the tools by typing “cd C:\Users\Username\Desktop\Pstools”, replace Username with your username and Pstools with the folder where you extracted the tools.
When you have navigated to the correct folder, copy the following command without the quotes: “psexec.exe -i -s %windir%\system32\mmc.exe /s taskschd.msc“.
Open the command window and right click, choose paste. Press enter.

Navigate to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator.

Right click the task called Reboot and click on Disable.
The task should now be disabled.

DriftyDonN

 

1 user thanked author for this post.

Rooker

Reply | Quote

I apologize for my previous message being so unclear.

My words are only the following:

“Im using ver1903 pro. The updateorchestrator section has 11 triggers, not just one!! The end result is feedback hub and you dont even have to sign in. FYI<It doesn’t work yet either!!”

I had worked all day trying to figure out why my pc kept waking up and until late in the day-approx 8 pm!- I had no leads. I suppose I thought the link would clarify any question about the author. I will be more careful.

Don

 

Reply | Quote

I use my workstation for music production. The Windows 10 1903/1909 update has degraded FireWire performance. I was getting audio dropouts because I have one external drive for audio that was connected by FireWire. Periodically, Task Manager would show the percentage of disk usage jump to 21-30 percent. When this happened audio dropouts occurred. This same external hard drive can be connected via USB 2.0. After I switched the drive to USB 2.0 the problem was resolved.

Unfortunately, I don’t know if Microsoft replaced the 1394 host controller driver, or if the updated OS build does not work properly with the older driver and perhaps throttles the disk access. In Device Manager:

IEEE 1394 host controllers
Texas Instruments 1394 OHCI Compliant Host Controller
Driver Version: 10.0.18362.1
Driver Date: 6/21/2006

I wish I knew what the driver version was under Windows 10 1809.

I have a second external drive that can only be connected by FireWire. I’ll replace it with a larger capacity drive that is Thunderbolt and/or USB 3.0 and transfer the contents to it.

Reply | Quote

There is a legacy driver which may help:  “1394 OHCI Compliant Host Controller (Legacy)”

For many people selecting the legacy driver resolves various FireWire issues. In my case, I’m not going to de-stabilize my working system. I’m just going to replace the one FireWire drive I have. The standard is being retired in favor of Thunderbolt and USB 3.0.

Reply | Quote

dwhitejazz wrote:

I wish I knew what the driver version was under Windows 10 1809

For Windows 10 1809 the base driver version (i.e. as first shipped) was 10.0.17763.1

[Note: There were a few increments to a couple of device drivers (e.g. bug fixes), for example  10.0.17763.348 (keyboard) and 10.0.17763.404 (Microsoft Usbccid Smartcard Reader] when 1809 was updated to build 17763.437.

I’m basing this on the PowerShell output of the following query on a laptop running Windows 10 Pro 1809:

Get-WmiObject Win32_PnPSignedDriver| select DeviceName, Manufacturer, DriverVersion

Unfortunately the laptop doesn’t actually include a Firewire port so there’s no specific mention of an IEEE 1394 host controller. Sorry…

Hope this helps…

Reply | Quote