J
JoseCaramelo Gomes
Hi
I'm having problems with an extremely slow boot (5 minutes or so) and with outlook search with a Toshiba Kira. I also have a Surface Pro 3 and the issue with outlook is the same.
So lets bring some details:
My Toshiba is an i7 with 8 Gb ram and 256 Gb SSD, running windows 10 version 1909. I have 45 Gb free space. (yesterday a MS Tec Advisor told me, after hours online, that I dont have enough free space!!!!).
I finally concluded that disabling Windows search in services solve the issue (10 seconds boot), but obviously I dont want to lose functionalities and I'm guessing this is probably some update issue (all updates installed for now, although there were issues with update KB4556799) and the setting "view update history" returns no history (whereas updates show in control panel under uninstall an update)
The issue with Outlook is already reported
After update, Outlook search reports "We're having trouble fetching results from the server..." on every search and the workaround solved the issue, but it is not fix.
Any ideas?
Continue reading...
I'm having problems with an extremely slow boot (5 minutes or so) and with outlook search with a Toshiba Kira. I also have a Surface Pro 3 and the issue with outlook is the same.
So lets bring some details:
My Toshiba is an i7 with 8 Gb ram and 256 Gb SSD, running windows 10 version 1909. I have 45 Gb free space. (yesterday a MS Tec Advisor told me, after hours online, that I dont have enough free space!!!!).
I finally concluded that disabling Windows search in services solve the issue (10 seconds boot), but obviously I dont want to lose functionalities and I'm guessing this is probably some update issue (all updates installed for now, although there were issues with update KB4556799) and the setting "view update history" returns no history (whereas updates show in control panel under uninstall an update)
The issue with Outlook is already reported
After update, Outlook search reports "We're having trouble fetching results from the server..." on every search and the workaround solved the issue, but it is not fix.
Any ideas?
Continue reading...