Windows 10: SearchIndexer.exe is preventing this device from being stopped

​

Safely Remove Hardware is a useful feature in Windows operating systems that lets users disconnect their external storage devices safely. To use this feature, right-click on your storage device in the File Explorer and select Eject. The same option is also available in the System Tray. If your USB device is busy, you will get […]

This article SearchIndexer.exe is preventing this device from being stopped first appeared on TheWindowsClub.com.

read more...

 

Built in device failure prevent windows 10 update to 20H2

I managed to update to Windows 20H2 successfully, tried to use Ztruker’s suggestion using PowerShell during restart but no go. So I stopped using Windows 10 Update Assistant and tried the other one he gave me using the ISO image and it succeeded.

I’ll list what I did in case it helps someone:

• Stopped Windows Update from downloading and installing drivers for the dead AMD card in Group Policy like this:
  Go to the section Computer Configuration -> Administrative Templates -> System -> Device Installation -> Device Installation Restrictions. Enable the policy “Prevent installation of devices that match any of these device IDs”.
• Used Microsoft Media Creation Tool to download the latest Windows (20H2).
• Disconnect from the internet to prevent downloading update or drivers.
• Mounted the ISO image, opened it and run Setup from within Windows.

This way prevented the downloading of a driver for the AMD card and made the update finish successfully.
When the update finished and desktop opened, I went to the Device Manager and the card wasn’t there and to Group Policy to check on device driver roll and it was there. Also all my apps and files were intact.


I wish to thank Ztruker and Try3 for helping me I appreciate it guys very much.

 

Is there anyway i can prevent tethering on win 7?

I did some digging and came across this:

Use Group Policy to prevent the installation of new network devices.

You'll find an option in Administrative Templates \ System \ Device Installation \ Device Installation Restrictions \ Prevent installation of devices using drivers that match these driver setup classes. From its description:

This policy setting allows you to specify a list of device setup class globally unique identifiers (GUIDs) for device drivers that Windows is prevented from installing. This policy setting takes precedence over any other policy setting that allows Windows to install a device.

If you enable this policy setting, Windows is prevented from installing or updating device drivers whose device setup class GUIDs appear in the list you create. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.​
Using policy settings here, you can either create a whitelist or a blacklist, either of individual devices or entire classes of devices (such as network adapters). These take effect when a device is removed and reinserted, so it will not affect the NIC built into the machine, provided you don't apply the setting to devices that are already installed.

You will need to reference the list of device setup classes to find the class for network adapters, which is {4d36e972-e325-11ce-bfc1-08002be10318}. Add this class to the blacklist, and soon afterward, nobody will be able to use USB network adapters.​
Of course, since he has administrator rights on the machine, there's a chance that he might find your Group Policy setting and delete it. Here's another angle of attack:

• Get/set the password for the local Administrator account.

• If he tethers his phone after you've said "no", issue a remote shutdown command to his PC.
  shutdown /s /m \\boneheads_pc

• Keep doing this until it sinks into his thick head that the house rules apply to him, too.

This will set you up with a battle of wills. I prefer Kursah's solution of revoking his admin privileges.

 

SearchIndexer (10048,D,23) Windows: The version store for this instance (0) has reached its maximum size of 128Mb

Ok so the solution was actually quite simple:

one simply need to rebuild the searchindexer cache:

So

1. Control Panel (View By Small Icon) -> Indexing Options
2. Press the "Advanced" button
3. Then press the Rebuild button

The problem stop showing up

Thanks!

Dany