A pending reboot is defined in many places. Scroll right to see the values and conditions. A Windows computer is pending a reboot if any of the conditions in this table are true.
Doing so will trigger Windows Search Indexer to cleanup obsolete artifacts and rebuild a new user catalog for the particular user. On the latest Windows releases (expected on 1809 and above, but subject to change) that has this feature, the registry key above is set to 1 after a catalog is successfully created. An absence of this registry key may indicate that the Windows version is older and lacks this newer feature.
If this key is missing, then it may still be possible to trigger a rebuild by deleting the following folder: C:\Users\<Username>\AppData\Roaming\Microsoft\Search\Data\Applications
NOTE: It is intended, but not yet validated, to keep the SetupCompletedSuccessfully registry key value change (as noted above) to serve this particular purpose for future versions. However, please note that the steps above are for troubleshooting/debugging purposes only (especially the second option for legacy behavior). We reserve the right to change this behavior at any time as necessary.
Note: for database size the following as values to use for estimates. Significant deviation from these values will typically be something to investigate.
Usually, 10-20K per indexed item would be estimated for database size.
For Outlook only data, use the higher side (20k) since they are pure text rich content
Virtual Machine Queue (VMQ) Mode in Network Adapter Driver
In some cases, if VMQ (Virtual Machine Queue) is enabled in a network adapter driver of a physical Hyper-V host, it may result in poor network performance in Hyper-V virtual machines. VMQ is a hardware feature and if it is not supported by your hardware but enabled in the driver, it can result in packet loss and increased network latency. The problem is typical to Broadcom Gigabit network adapters and occurs in all Hyper-V versions (Windows Server 2012 R2/2016/2019).
VMQ is designed to improve network performance by directly forwarding packets from a physical network adapter to virtual machines.
You can disable VMQ in the properties of your network adapter driver.
Or you can display a list of network adapters with VMQ support and their status using PowerShell:
Get-NetAdapterVmq
To disable VMQ for a specific NIC, run the command below (the network adapter will be unavailable for a couple of seconds):
Set-NetAdapterVmq -Name “NICName” -Enabled $False
After disabling VMQ, it is better to restart the host and check the network performance.
Optimize TCP Settings for Hyper-V on Windows Server 2019
Save the current TCP settings on your Hyper-V host and apply new settings that will make TCP settings in Windows Server 2019 almost similar to those of Windows Server 2016.
By default in Windows Server 2019 and Windows 10 1709+, the CUBIC implementation of TCP is used. This algorithm is optimized for high-speed networks with high latency (it is also used by default in Linux kernel 2.6.19 and newer).
Apply the following settings only in Windows Server 2019 or Hyper-V 2019.
Type cmd, right-click on Command Prompt, and then click Run as administrator
Copy and paste the following: explorer shell:::{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9}
Press Enter
Select "Always show all icons and notifications on the taskbar"
Click OK
If the checkbox "Always show all icons ..." is greyed out, I'm not totally sure what fixed it yet but it appears that changing the EnableAutoTray value in the Regedit helped.
