Outlook not updating gmail Offline#

However i now have a new direction to look in and will do more research along those lines. Your solution involves getting rid of chrome which we cannot do. I too found the commands to manage and report on the BITS service and learned lots about what was going on. I too came to the conclusion that my address book downloads (OAB) and outlook no longer receiving mail when waking up from sleep had to do with BITS. i too have been working on this problem for the last 6 months. ItвЂ™s worth noting that re-installing Google Chrome will cause this problem to re-occurД¬hristwest, VERY interesting.

Outlook not updating gmail Offline#

Send/receive > send/receive groups > download offline address book > ok Open outlook, and manually download the offline address book.

You should now see the chrome component updater is no longer thereД¦. Open windows PowerShell and run the command: Open windows PowerShell as an admin and use the following command:ДҐ. locate background intelligent transfer service > properties > change startup type to manual.ДЈ.4. *note* if these commands donвЂ™t work, for example it just hangs, follow the below steps:ДЈ.2. Get-bitstransfer -allusers | remove-bitstransfer Open windows PowerShell as an admin, and use the following commands: It is critical that Google chrome is not a part of your Group Policy, as this wonвЂ™t work otherwise, as chrome will automatically reinstallДЈ. But as the BITS cycle resets, the chrome component updater begins attempting to run a download, causing the problem to re-occur almost instantly.ДЎ. When you close and reopen outlook, this resets the BITS cycle, allowing the emails to come through. This causes the offline address to fail its download, causing outlook to fail syncing emails. The job created by the chrome component updater doesnвЂ™t get deleted even after Chrome has been uninstalled. The issue is a problem with the Chrome component updater causing the BITS service to go into an unresponsive state. We had this problem for 6 month until we found a fix! I hope this helps. This is the solution to an ongoing issue affecting many users/companies.