By: Waseem Patwegar
In case your computer’s clock is slowing down or showing incorrect date and time, you should first try to fix the clock on your Windows Computer by re-synchronizing with an online date and time service, before exploring other options.
Windows Computer Clock
Located at the bottom right corner of your screen, the Clock on Windows Computer is designed to automatically set its date and time clock accurately by synchronizing with its default timekeeping server (time.windows.com). For this reason, you never have to worry about setting the date and time on your computer, not even during yearly Daylight Saving Changes.
However, at times your computer may start displaying incorrect date or time. This can happen due to hardware issues, Online synchronization problems and also due to the presence of viruses on your computer.
Fix Slow or Incorrect Windows Computer Clock
As mentioned above, the first approach in this case would be re-synchronizing your Windows computer with an online time server and see if this fixes the problem.
1. Right click on Windows 10 Start button and click on Control Panel
2. On the Control Panel Screen, look for Date and Time and click on it.
3. On the Date and Time screen, click on the tab labelled Internet Time (See image below)
4. Next click on Change Settings button (See image above)
5. On the next popup window (Internet Time Settings), make sure that the little box next to Synchronize with an Internet time server is Checked (See image below)
6. Next, click on the down arrow and select a time server from one of the available ones. You can stick to the default Microsoft Time Server (time.windows.com) or choose another server.
7. Once you’ve made your server selection, click on Update Now button to start synchronization.
The synchronization process should be over within a few seconds and your computer may report “The clock was successfully synchronized.”
8. Click on OK to close the window.
Make Windows Time Service Automatic
The problem of an incorrect clock on a Windows computer can be due to Windows Time Services not being set to Automatic option.
1. Press Windows + R buttons on the Keyboard of your computer to bring up Windows Run command Window.
2. Type services.msc in the Run command box and click on OK .
3. On the Services window, locate an entry labelled Windows Time in the Name column (See image below).
4. Double click on Windows Time and click on Properties .
5. On the next window, change the Startup type to Automatic (in case it is already not set to Automatic) and click on Start in case you find that Windows Time Service has not been started.
Now, start monitoring your computer’s time for a few days. In case the computer clock starts losing time again, the problem may be due to one of the following issues.
1. CMOS Battery
CMOS which stands for ‘Complementary Metal-Oxide Semiconductor’ is a static Random Access Memory device that stores the BIOS values for your computer, including date and time information.
The CMOS chip is powered by a battery so as to keep the BIOS data active even when the computer is turned off and not connected to a power supply.
When the CMOS battery goes bad or comes to the end of its design life, CMOS chip starts losing information and this is indicated by a slowing clock on your computer.
The simple solution in this case is to replace the CMOS battery with a new one. CMOS batteries are inexpensive and very easy to replace in the case of desktop computers.
However, replacing a CMOS battery on a laptop is not easy. Depending on the make of your laptop, you may find it difficult to open the outer case and access CMOS battery in its cramped location.
2. Viruses and Malware
In case your computer starts losing time even after a CMOS battery replacement, the problem may be due to presence of Malware or Viruses on your computer.
To fix this problem, make sure that the Antivirus program on your computer is up to date. If not, run an update to make virus definitions up to date and scan the computer for malware.
You can use the in-built scan function that comes with most Antivirus programs like Norton or use Microsoft’s free Malware Removal Tool to scan for Malware and fix the problem.
I had try many methods but failed to start the service to synchronize time.
I’m unable to log on in the service.msc as well.
Greetings! I am Vijay, an Independent Advisor.
1. I assume that you have logged in using admin rights.
4. You should run Malware Bytes
Malware Bytes – https://www.malwarebytes.com/
1. Set Synchronize with an Internet Time Server
Right click on the date / time in notification bar > Adjust date & time > Make sure Set time automatically and Set time zone automatically are set to ON
Windows Key+ i > Time & Language > Click Region > Scroll down > Click Additional date, time & regional settings > Click set the time and date > Under Internet Time tab > Click Change Settings > Check Synchronize with an Internet Time Server (You can also try to change to pool.ntp.org and click Update) > If it is already checked, uncheck it and OK > Now go back to this and check it again
2. Fix Windows Time in Services
Type services in Windows Start Search box > Click Services > Scroll down to reach to Windows Time > Double Click to open > Set Startup type to Automatic >
Reboot your computer
3. Try some other fixes mentioned here
(Ignore Download this PC repair tool. This is not recommended by experts)
Disclaimer – This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
I managed to successfully update to 20H2 from 1909, on my Asus Laptop, after facing some problems.
It seems like a lot of people are having the same issues and are finding that they are related to Conexant/Synaptics Audio Drivers.
I attempted to update the normal way via settings and updates however it was stuck at 61% “Installing”.
What I did was uninstall all audio driver related programs (Bose App, Sennheiser App etc.) and then uninstalled the Conexant HD Audio Drivers and Intel Display Audio Drivers from Device Manager. (under sound, video and game controls)
Then I turned Wifi off. And made sure that the computer would not connect to the internet after a restart.
(To prevent re-installation of those drivers)
Then I went back to settings (with wifi off and drivers uninstalled). The update went past 61% and completed installing. It then asked me to restart, then completed the update.
Also. If you have any other solutions/advice to this fix on different hardware please reply below as I hope other people will find this information valuable.
Thanks for reading.
P.S. I found this on the HP Support page and found it useful as I adapted it to fix my Asus Laptop:
“I finally managed to crack it! I am now running 20H2 on my HP ZBook Studio G3! The problem are those pesky Synaptics/Conexant audio driver(s). But lets start from the beginning: Running HP Support Assistant yielded no updates. Running HP Image Assistant only reported those faulty update packages I mentioned earlier (which doesn’t update anything when run):
· Synaptics WBF Fingerprint Driver
So no real updates there. BUT when I manually compared the driver version of “Conexant ISST Audio” in device manager compared with the version sitting on the drivers download page for my computer, they were different. The drivers download page says that SP109031 ( https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-zbook-studio-g3-mobile-workstation/893. contains version 10.0.3690.0. So I manually downloaded and installed it, but property page in Device Manager now reports 18.104.22.168, not 10.0.3690.0, but still it was different from before. Feels like the quality of drivers and their versioning is far from great . So tried running Windows Update again but still got stuck at 61%. So I dug deeper into the logs of Windows Update and saw the last thing it mentioned before getting stuck was “HP Dock Audio”. I use the “HP ZBook Dock with ThunderBolt 3″ and it turns out that it also uses a Synaptics/Conexant audio driver, only device is rebranded as HP Dock Audio. I had driver version 22.214.171.124 i nstalled (seen on Property Page in Device Manager), and it’s from 2019-11-21 and I’ve had that for a long time, and a newer version can’t be found at the HP drivers download page for that product. Neither could it find an update when trying to run “Update driver” on the property page in Device Manager. So in device manager, I instead right-clicked “HP Dock Audio” and clicked “Uninstall device”, and made sure to select the “Uninstall drivers” option that is presented next. Then before rebooting, unplugged the dock connector (in my case the multi-cable with both charging and the USB-C connector), and instead connected only the charger/power supply. After a reboot I ran the Windows Update again, and now it got passed 61% and after more than 1 hour it finished the feature upgrade to 20H2 (I had 1909 before upgrade). When I then plugged in the dock, after the finished upgrade, Windows suddenly decides to install another driver for the HP Dock audio device, a Microsoft driver which seems to be a generic USB Audio driver. But it works. Looks like HP+Synaptics didn’t do t heir part so Microsoft stepped up and did the work for them. So problem was probably the two Conexant drivers – Both the Conexant ISST Audio device for built-in audio, and the HP Dock Audio device for the HP Thunderbolt dock.
Hope this can help someone else as well! And if someone at HP is reading this – shame on you for not providing a fix for this! And if someone at Microsoft is reading this – why haven’t you provided a workaround for this or published information on how to do it. And publicly shamed HP+Synaptics for t his mess. This problem has been with us for about a year since it also faulted the 2004 feature update (already insider builds).”
More than five years after Windows 10 launched, Microsoft has never managed to curtail one of the operating system’s most annoying features: its willingness to restart the computer while work is being done. For all the company’s claims about how it has optimized this process, it pretends not to understand that users generally hate forced reboots.
As Sean Hollister points out for The Verge, he had actually been in the process of writing about Microsoft’s new habit of force-installing links to the Progressive Web Application (PWA) versions of its Office suite. PWAs are applications that are supposed to behave like a native application despite running in a browser window. Hollister got up to eat dinner, came back to his desk, and found his own machine had forcibly restarted, leaving him with — you guessed it — the same PWA applications.
Microsoft is once again distributing its software like malware. While I am not accusing Microsoft of shipping a trojan, applications that forcibly install themselves without user consent are, in fact, malware. There’s nothing new about the apps themselves; they’re the same version of Office you could previously use online. The difference is, now they’ve stuffed themselves into the Start Menu so Microsoft can advertise its cloud services to you. Satya Nadella, Microsoft’s CEO, has made Azure a major part of Microsoft’s business going forward, to the point that the company claims Amazon and Facebook are its major gaming competitors rather than Sony and, to a lesser degree, Nintendo. This is, presumably, part of the effort to shove users into new paradigms of usage.
It’s Your Computer, Not Microsoft’s
Hollister acknowledges that putting web links in the Start Menu is a fairly mild annoyance, but writes:
[T]hey’re the latest proof that Microsoft doesn’t respect your ownership of your own PC, the latest example of Microsoft installing anything it likes in a Windows update up to and including bloatware, and the latest example of Microsoft caring more about the bottom line than whether a few people might lose their work when Windows suddenly shuts down their PC. Luckily, I didn’t lose any work today, but a friend of mine recently did:
Once again, @Windows has restarted without notifying me and caused me to lose some work.
I was typing note in Notepad, but had not yet transferred it to a Google Doc. Got up to get some water, when I came back my PC was rebooting. Text is gone. cc @StarFire2258 because ugh this
— Sean Buckley (@seaniccus) October 4, 2020
Given Microsoft’s ongoing and presumably permanent hostility towards user control, I’d like to take a moment to inform readers of a utility called the Windows Update Blocker (WUB). The Windows Update Blocker does exactly what it says on the tin: It prevents Microsoft from ever rebooting your PC to install updates or installing updates without permission.
There are real reasons not to use this utility. If you activate this utility and do not regularly turn it off to allow the machine to receive security updates, you risk being unprotected when new vulnerabilities appear. It’s a bad idea to turn Windows Update off and then forget to update manually, so if you choose to go this route, you may want to set a periodic alert to remind you to update every few weeks or months. It’s possible for a person to actively want to be updated as soon as patches arrive while refusing to allow Microsoft to reboot their system out from under them.
I disable Windows Update on all testbeds after patching them up because I’ve been burned before by having an update arrive 5-10 days after I configured the system. I’ve been in the middle of 6-8 hour benchmark runs (SPEC Workstation takes a while) and had the system rebooted out from under me, forcing a complete restart of the tests from scratch.
It is not sufficient to define “Active Hours.” It is unreasonable to expect people to keep an exact log of what their Active Hours at all times so they can remember to change them while working late. It is, apparently, too much work for Microsoft to program Windows not to reboot a computer outside of Active Hours if the keyboard is in use, or if the CPU and GPU are both loaded. I can understand why this might be so — the company might be afraid of malware deliberately loading the CPU and GPU as a way to keep Windows Update from running.
But if this is true, the correct way to deal with it is to present the user with a periodic message that says “Windows Update has not rebooted to install patches because you appear to be using the computer. Please schedule a time to reboot or press the ‘Delay’ button to see this prompt again in 4 – 24 hours.” The only thing Microsoft needs to do to fix this problem is bring back a feature that used to be a staple of Windows: The ability to delay a reboot. In Windows 7, if the “A restart is required” prompt popped up, and you didn’t answer it, the machine assumed that it should not restart.
I’m not recommending that people install the Windows Update Blocker, because it’s bad policy to recommend people make their computers less secure, as if this carried no potential downsides. But given Microsoft’s behavior and its significant, negative ongoing impact on end-users, it’s time to talk about solutions, even imperfect ones. Windows Update Blocker won’t prevent Microsoft from eventually installing its malware-ish PWAs, but if you delay the installation until you’re ready to deal with it, you’ll at least know what you’re getting into and where the problems are. PWA installations, incidentally, can be removed in the “Add/Remove Programs” section of Settings or Control Panel.
The correct answer to the question “When is it acceptable to reboot the user’s computer without permission?” is “Never.” Microsoft would like to pretend otherwise. Everyone deserves the right to decide if they want to rent a PC that Microsoft retains control over, or if they prefer owning it themselves. The only time it ought to be permissible to reboot or shut down a computer without the consent of the user is if shutting the machine off is the only way to prevent thermal or electrical damage. In those circumstances, the CPU has far faster reflexes than any human could match. In every other situation, consent should be required.
If Windows can reboot at will through a process I have no opportunity to interrupt, I’m not the person in control of the PC. Until and unless Microsoft wants to start paying me to use one, they’ve got no right to interfere in how it operates.
High disk usage can bog down your system
A slow-running computer often bogs because Windows commits significant system resources into disk read and write operations. When you open Task Manager and see 100% disk usage, stopping the process that’s forcing that use brings Windows back to normal working order.
Many of the following fixes for 100% disk usage in Windows 10 are relevant to Windows 10, 8, 7, and Vista. However, some commands and system settings may vary.
Causes of High Disk Usage on Windows 10
There are several potential causes for high disk usage in Windows 10, but most come down to the same basic idea: Too many things are running for the computer to handle.
One common cause is swapping or paging. Swapping occurs when a computer runs out of physical memory (RAM) and needs more space to store information about the running processes and applications. It uses a file on the hard drive called swapfile.sys to hold it. As Windows works with that information, it constantly reads and writes to swapfile.sys, driving up disk usage.
You also might find that applications that search through or use many files at once access the hard drive at an alarming rate behind the scenes. Many applications can behave this way, including antivirus software and some utilities that are installed with Windows.
How to Fix High Disk Usage on Windows 10
Most of the time, the fixes for high disk usage come down to finding the process that uses the hard drive frequently and stopping it. Below are a few of the most common solutions.
Disable Windows telemetry. Windows 10 collects data about the way you use it in the background. It’s been the topic of controversy for privacy reasons, and it’s a common cause of high disk usage. Disabling the service responsible can help give the hard drive a rest.
Disable Windows search indexing. Windows keeps track of your files and where files are located on the drive, so you can easily search for the file you need. Sometimes, the process Windows uses to create an index of where those files are can slow down the drive. Disable search indexing to decrease stress on the drive.
Disable SuperFetch. The SuperFetch utility runs in the background on Windows, analyzing RAM usage to see which apps use the most. SuperFetch can use a lot of system resources, including writing to the drive frequently. Disable it to stop the process from running behind the scenes and writing to the drive.
Disable Windows Tips. As you use Windows, an integrated app running in the background offers notifications with advice about the operating system. While this is the least likely problem causing the disk usage utilization error, it is one more app running in the background that can cause problems. Turn off Windows Tips and see if it improves your system performance.
Give Skype write permissions. If you run Skype for Desktop on any Windows version before Windows 10, Skype could be causing the disk usage problem. If Skype doesn’t have permission to write data to one of its subfolders in Program Files (x86), it continues to write and ramps up hard drive usage.
To change permissions, right-click Skype.exe in C:\Program Files (x86)\Skype\Phone\, then go to the Security tab and select Edit. Next, choose All Application Packages, then select the Write check box under Allow. Finally, to close, select OK.
Disable prefetch in Chrome. A few features in Chrome speed up your browsing experience. One of those services is a prediction service in Chrome that analyzes what site you’re likely to visit and preloads those pages in the background. However, this service puts an extra load on your computer and the hard drive.
In Firefox, disable prefetching by visiting about:config in the address bar and setting the network.prefetch-next value to false.
Fix the AHCI driver. Microsoft acknowledges a known bug with some Advanced Host Controller Interface PCI-Express models on Windows 10. If your computer is affected, you’ll experience 100% disk usage problems. To fix it, do the following as described below.
First, check that your computer has the AHCI driver by opening the Device Manager and looking at the item IDE ATA/ATAPI. If you see SATA AHCI Controller, open it and select Properties. Under the Driver tab, choose Driver Details. Here, look for the driver storahci.sys. If you see it, then your PC could be susceptible to this known bug.
If you discovered that the storahci.sys driver file is on your system, change its value in the Registry Editor. Go to Details in Device Manager and choose the Device instance path from the drop-down menu. From here, copy the value listed and paste it into a text editor like Notepad.
Next, open Regedit and browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\PCI\. Expand the folder of the value you saved in a text editor. Inside this folder, open Device Parameters\Interrupt Management\MessageSignaledInterruptProperties, double-click MSISupported, and change its value to 0.
Editing inside the registry opens the door to inadvertent, significant configuration errors. Changing the wrong values may destabilize your computer. Make a backup of the registry by clicking File > Export and saving the .reg backup file to a folder or external hard drive.
Add more RAM. If disk usage is high because your computer doesn’t have enough physical memory (RAM), the best solution is to add more. RAM is one of the easiest upgrades on any PC, and it’s relatively inexpensive. Plus, your computer will be able to multitask more efficiently as a result.
Disable automatic Windows Updates. Another common cause of high disk utilization sources from Windows Updates taking place at random times, automatically. Stop Windows from updating at random, and you’ll stop the drive from maxing out.
If you disable automatic Windows Updates, run manual updates frequently. This process ensures you receive important security updates that keep your computer safe from viruses and malware.
Scan for malware. If all else fails, there’s a chance your computer could have a virus or malware. The best thing to do at this point is to make sure you have good antivirus software and run a full system scan. A full scan can take a long time, but it finds and removes any malicious software running on the system and spiking the disk usage.
Is your PC taking minutes instead of seconds to boot after installing Windows 10? We have some solutions
Many people who upgraded from Windows 8 to Windows 10 have suffered from massively lengthened boot times. The symptoms for this particularly curious bug include a black screen after seeing the Windows loading animation and your PC manufacturer’s logo, and the ability to move your cursor around the black screen but an inability to do anything else. For some, this process can take in excess of a minute.
In our testing, we found two laptops that suffered from this problem. A Dell Inspiron 17 from 2013 and an Acer Aspire V5, also from 2013. The Acer added more than a minute to its initial boot time, while the Dell laptop’s boot time shot up by 25 seconds, time that was mostly spent staring at a black screen.
There are various fixes we’ve seen working on our own laptops, and we’ll start with the simplest first and escalate to more involved methods. Credit to the users on the Microsoft Community .
Enabling/disabling fast start-up
We were largely able to fix the sluggish boot speeds of our Acer Aspire V5 by disabling Windows 10’s fast start-up feature. To do this, o pen the Start Menu and type “power options” and select Power Options when it appears. When the Power Options window opens, select “Choose what the power button does” from the list on the left of the window.
If you see a small blue and yellow shield icon and the text “Change settings that are currently unavailable”, click the text. You may need to enter your password or your PC administrator’s password to do this. Now scroll down to the Shut-down settings list. Untick “Turn on fast start-up” and click Save changes. When you next switch on your PC you should immediately see a significant boot time cut. With our Acer laptop, the boot time dropped by 80 seconds. Most interestingly, switching Fast startup back on made no difference; it would appear that the simple action of turning fast start-up off and on again is enough to get Windows 10 out of its slow booting state, in this case at least.
The Dell Inspiron 17 proved to be much more troublesome, and while the methods below have apparently worked for many people online, it didn’t fix out issue.
Some have theorised that the black screen before boot is a graphics driver problem that has been particularly bad for those on laptops that switch between Intel HD Graphics and a dedicated card from Nvidia or AMD. An easy way to verify this is to disable your AMD or Nvidia graphics driver and restart your computer. To do this, right-click on the Start Menu icon and click on Device Manager.
Click on Display Adapters and identify your dedicated graphics card. It’ll be labelled Nvidia, AMD Radeon or ATi Radeon. Right-click on the graphics card and click “disable”. This may cause your screen to go blank for a moment. Shut down your PC (not restart) and turn it on again to see if this has fixed the problem.
If you only have Intel HD Graphics, you do not need to do this. If it is your graphics card that’s causing the problem, re-enable your graphics card using the steps above and then download the latest version of your card’s drivers from the manufacturers’ websites – amd.com/drivers or nvidia.com/drivers. If you’re not sure which driver to download, just select the option that automatically finds which card you’re using. Once these drivers are downloaded and installed, shut down and restart your PC to see if the problem has been solved.
If you’re still experiencing a slow boot, it’s worth re-checking whether toggling fast start-up off and on is more effective with your new drivers.
AMD power saver
If you have an AMD graphics card, there is one more step you can try. Go to the Start Menu and type “regedit”. Open regedit and click the Edit button at the top of the screen, then click on Find. Type “EnableULPS” and click “Find Next”. EnableULPS will be highlighted in the list of registry options.
Double click it, and change the value from 1 to 0. This will disable a power saving feature that switches off your dedicated graphics card when it’s not needed and this will mean your laptop consumes more battery power, so only do this if your laptop spends most of its time plugged in.
If all else fails.
If none of the above solutions work for you, you have a choice. You can either downgrade back to Windows 8.1 or Windows 7 (if you installed Windows 10 less than a month ago) or restore Windows 10 to its default settings, removing all your files and programs. To do this, search for “reset” in the Start Menu and click on Reset this PC, then Get Started if you want to reset Windows 10 or the other Get started option if you want to downgrade to Windows 8 or 7. You can also do a clean install of Windows 10.
If you’re going to do a complete Windows 10 reset, make sure all your files are backed up as they will all be lost in the reset process. In addition, if you choose to reset Windows 10, you will lose the option of going back to Windows 7 or 8 forever, so you may end up being stuck with Windows 10 unless you have a Windows 7 or 8 system image or restore partition.
For us, resetting Windows 10 completely was the only way to solve our boot issues on our Dell laptop. The boot issues still remain when you restart the PC, but as long as fast start-up is enabled, each time we boot up the PC, we no longer see the black screen. In addition, you can skip all of this entirely by choosing to put your computer to Sleep instead of shutting it down every time you’re done using it.
Last updated: July 14, 2020 10:00am PST
This issue is now resolved. Please see the Next Steps section for more information.
After updating to Windows 10, version 2004, some older devices or devices with certain older apps installed that use legacy file system filter drivers might be unable to connect to OneDrive via the OneDrive app. Affected devices might not be able to download new Files On-Demand or open previously synced/downloaded files.
Affected devices might receive the error, “OneDrive cannot connect to Windows. Files On-Demand require a connection to Windows in order to show your files without taking up space on this device. OneDrive can keep trying to connect to Windows or you can choose to download all your files. You won’t be able to use online only files until this is fixed.”
Note Some or all of your files may have been downloaded locally if the Download Files button was selected on the above error dialog.
Workaround using Troubleshooter
A recommended troubleshooter has been released to affected Windows 10, version 2004 devices to restore access to Files On-Demand. Depending on user settings, the Troubleshooter might run automatically. If you are prompted to run the troubleshooter, it is recommended that you allow it to run. You can verify the troubleshooter has run by following these steps:
Select Start and type: troubleshoot
Select Troubleshoot Settings.
Select View History in the Troubleshoot section of the Settings dialog.
If the troubleshooter has attempted to run, you will see a recommended troubleshooter with the title, Files On-Demand troubleshooter and description You may have lost access to your Files On-Demand. This troubleshooter restores access or prevents the loss of access from happening in the near future. Important: Please reboot your device once the troubleshooter is finished.
If it was able to run successfully, it will say, Successfully ran on with the date it ran on. If it was not able to run successfully, it will say Could not be run on with the date it ran on.
Important If your device has not been restarted since the troubleshooter was run, you will need to do so before following the rest of the steps to complete the mitigation.
Important To verify Files On-Demand is still enabled, right click or long press on the OneDrive icon in the notification area, and select Settings.
In the OneDrive dialog, select the Settings tab and verify that Save space and download files as you use them is enabled, then select the OK button.
If you are using more than a single OneDrive account within the app or are using both OneDrive Personal and OneDrive for Business, you will need to repeat steps 5 and 6 for each account.
OneDrive app should now connect and run as expected.
Important: If your device is affected by this issue and the troubleshooter automatically ran successfully, you will still need to manually perform the above steps starting at step number 6.
Workaround using manual steps
To mitigate the issue on Windows Server, version 2004 or if the troubleshooter has not run, use the steps below:
Select the Start button and type: cmd
Right click or long press on Command Prompt and select Run as administrator.
Type or copy and paste the following command into the Command Prompt dialog: reg add HKLM\System\CurrentControlSet\Services\Cldflt\instances /f /v DefaultInstance /t REG_SZ /d “CldFlt”
Restart your device after the command has completed.
To verify Files On-Demand is still enabled, right click or long press on the OneDrive icon in the notification area and select Settings.
In the Settings dialog, verify that Save space and download files as you use them is enabled, then select the OK button.
If you are using more than a single OneDrive account within the app or are using both OneDrive Personal and OneDrive for Business, you will need to repeat steps 5 and 6 for each account.
OneDrive app should now connect and run as expected.
When following the above steps in the Workaround using Troubleshooter section, you might see a Could not be run message for a critical troubleshooter with the title Hardware and devices. This is an indication that your device is not impacted by the Files On-Demand issue. The Files On-Demand troubleshooter is not needed and will not run. You should not need to restart your device or follow any of the steps after step 5.
You can also access or download files within your web browser using the OneDrive webpage. Files manually downloaded from the OneDrive webpage will not be synced automatically and will need to be uploaded manually.
This article describes the Microsoft policy in response to daylight saving time (DST) and time zone changes.
Subscribe to the Microsoft Daylight Saving Time & Time Zone Blog to receive the latest updates on changes around the world.
Applies to: В Windows 10 – all editions
Original KB number: В 22803
Microsoft policy in response to daylight saving time and time zone changes
Many applications and cloud services reference the underlying Windows operating system for daylight saving time (DST) and time zone (TZ) information. To make sure that Windows has the latest and most accurate time data, Microsoft continuously monitors DST and TZ changes that are announced by governments around the world. Microsoft makes an effort to incorporate these changes to Windows, and publishes an update through Windows Update (WU). Each DST and TZ update that is released through WU will have the latest time data and will also supersede any previously issued DST and TZ update.
In order for Microsoft to provide an update at the earliest and ensure a seamless transition to new DST and TZ policies, Microsoft recommends that governments provide the following:
- Ample advance notice (one year or more) of the planned change
- Official published confirmation of planned changes to DST or time zones
- Concentrated efforts to promote the change to affected citizens
KB 914387 provides a list of DST updates that have been released. It also includes a short summary of the content that is included in each update. This allows a consistent means for customers and partners to be informed whenever such an update is made available.
DST updates are also included in monthly rollup releases. You can find more information about our monthly rollup releases here:
Microsoft DST and TZ support policy
|Change type||Change details||Microsoft support policy||Solution|
|Change to a region’s time zone rules||A subset of the region that shares a time zone makes a change to its DST requirements or changes the time bias of its time zone. A new time zone is required for the affected users within that region because the existing time zone has to remain unchanged for the rest of the users.|
A new Windows time zone entry will be created only when a country or region (including dependencies), or a first-order administrative division of a country or region (state, province, department, and so on), has a separate and distinct history of UTC offsets and DST rules from existing TZ entries. Additionally, a smaller geographic area (county, city, and so on) qualifies for a new Windows time zone entry when its current UTC offset and DST rule combination is not provided by another Windows time zone entry.
Troubleshooting tips to get you back on track
The search tool in Windows 10 has, with different feature updates of the operating system, both increased and decreased its integration with both Cortana and with File Explorer. These often-shifting changes to how search works leads to glitches—some of which present an easy fix.
These instructions apply to all versions of Windows 10.
Causes of Windows 10 Search Problems
When Windows search isn’t working, it’s almost always a simple software problem. The system may just need a restart to get it working again. Other possible causes could be network-related or the search system itself having a service interruption.
How to Fix Windows 10 Search Problems
You’ll use a lot of the same methods to fix problems with search as other minor errors. Here are some options to try and get the system back to work.
Check your network connectivity. If you aren’t connected to the internet, Windows 10 search won’t work. Before you try anything more serious, make sure your network is functioning properly.
Restart your device. It’s basic advice, but there’s a reason it’s the first port of call for most Windows errors—reboots often work wonders. If you haven’t tried restarting your device, do so now, as a simple reboot of the system flushes memory and disk-cache glitches that adversely affect system performance. It’s better to perform a restart than shut down too, as shutdowns occasionally send your Windows 10 PC into hibernation mode.
Turn Cortana off and on again. Since Cortana is so entwined with Windows 10’s search function, turning it off and on again sometimes corrects Windows 10’s file-search problems.
Run Windows Troubleshooter. Microsoft’s Windows troubleshooter may not be able to fix every problem it comes across, but it can often send you in the right direction to learn more or at least pinpoint what the actual problem might be. The same goes for problems with the Windows 10 search bar not working.
Open the troubleshooter by opening the Start menu and going to Settings > Update and Security > Troubleshoot > Search and Indexing. Click the Run the troubleshooter button to go through the diagnostics.
Verify the Search service is running. It’s possible the Windows Search service itself has been disabled for some reason.
Press Win+R to open the Run window, then type “Services.msc” and press Enter.
When the Services window appears, scroll down the list of services to find Windows Search. If it’s already running, right-click it or tap and hold, then select Restart. Alternatively, if it’s disabled or has a blank Status, right-click or tap and hold, then select Start.
Rebuild the Windows 10 search indexing options. It may be that Windows 10 has forgotten where certain files and folders are. To help it remember, rebuild its indexing options. Start by accessing the Control Panel in Windows 10.
Select Indexing Options from the main menu icons, and then click Advanced. In the Advanced options, Click Rebuild.
The rebuilding process may take a short time to complete depending on the size of your drive and how full it is.
If none of the above tips helped get your Windows 10 search bar working again, try some more advanced Cortana help tips or opt for a full Windows reset.