Category Archives: Windows

windows10专业版控制面板没有bitlocker

惆怅了很久,反复确认了版本是pro,也尝试了搜索,metro能搜到bitlocker但无法打开,控制面板直接搜索搜不到bitlocker,右键盘也没有bitlocker,找了一圈,答案很简单:启动shell hardware detection服务。

不明觉厉,之前任何一个版本禁用都毫无影响

副作用:驱动器个性化图标都显示出来了

windows10 快速访问无法展开

快速访问固定了不少常用文件夹,无法使用很蛋碎

尝试了清历史记录,设置里禁用显示最近使用和常用文件夹,还是不行,最后无意间看到资源监视器里一直在读写莫个文件,想起来尝试下,就动手干掉了下面这个文件夹的所有内容

%userprofile%\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations

 

然后就没有然后了

a fix to windows update can’t check updates restart computer…

The following may be recorded in Application Logs

wuaueng.dll (948) SUS20ClientDataStore: Unable to read the header of logfile C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log. Error -546.

Application ESENT 412 Logging/Recovery Error

Fix:

stop windows update service and delete X:\Windows\SoftwareDistribution directory then start windows update and go get some snacks while windows is checking and downloading updates.

Cluster resource ‘Virtual Machine XXX’ of type ‘Virtual Machine’ in clustered role ‘XXX’ failed in windows 2012 hyperv cluster

Cluster resource ‘Virtual Machine XXX’ of type ‘Virtual Machine’ in clustered role ‘XXX’ failed. The error code was ‘0x80004005’ (‘Unspecified error’).

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

–AND–

Live migration of ‘Virtual Machine VM’ failed.

Virtual machine migration operation for ‘VM’ failed at migration destination ‘HYPERVHOST’. (Virtual machine ID AFDD9E40-58EF-4364-AF83-0EA9F4B54C0E)

The virtual machine ‘VM’ is using processor-specific features not supported on physical computer ‘HYPERVHOST’. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID AFDD9E40-58EF-4364-AF83-0EA9F4B54C0E)

—–

This may happen if you are running hyper-v cluster with different hardware especially you are mixing up a latest server and a old box.

Just shutdown the VM and open settings in cluster manager, make sure Migrate to a … is selected under Processor>Compatibility