Windows 10: Silly Question in Regard to Closing Conhost.exe Main Question at the Bottom

I typically have 2 instances of Conhost running at all times, 1 for System, and 1 for User; after updating Office 365, I saw that the extra Conhost and extra ClickToRun's it had created weren't going away even after 40 minutesso I closed the extra C2R processes but I didn't know which conhost was the extra, since there were 2 System ones and only 1 User one. I closed the User one, and then realized it was the other System conhost that I wanted to closeafter I shut my PC down to restart, the VGA light on my motherboard hung and I failed fast startup; this has nothing to do with closing conhost,

:)

 

conhost,exe using IMMENSE amount of memory.

Hello, I'm Greg, here to help you with this.

1) Try these fixes for high CPU usage by conhost.exe:

Conhost.exe: How to Fix Console Window Host High CPU Usage

https://wethegeek.com/what-is-conhost-exe-and-w...

https://www.thewindowsclub.com/conhost-exe-windows

(Avoid ad links which intrude into editorial copy, especially DO NOT INSTALL Restoro, PC Repair Tool and Reimage ads)

2) Go over Windows 11 with this Performance Checklist to try to find and fix problems:

https://answers.microsoft.com/en-us/windows/for...

Feel free to ask back any questions. Based on the results you post back, I will have other suggestions if necessary.

____________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

 

Silly Question

Hi Sturner33333,

no such thing as a silly question, only silly answers.

click on the pen icon again to turn it off then you can drag the map.

please let me know if that is not what you were looking for.

 

Questions regarding sysprep and capture in MDT

I have a question regarding the sysprep and capture function in MDT 2013.

I have done a sysprep & capture on a Windows 10x64 machine with software and drivers included using MDT.

So the next step I did was to deploy the captured .iso file onto a new machine which had the usual configuration steps including setting up the computer name, timezone and keyboard layout etc and everything was start up fine and all the software and drivers were also configured & installed properly.

However, the issue is that machine's SID and computer name were completely the same as the one I ran the sysprep & capture on. Was this supposed to be like this? Because I did some research and a sysprep is supposed to change the SID as it is treated as a new machine. Also, I did configure a new computer name for the machine during the deployment setup but I have no idea why its the same name as the other machine.
I would appreciate any answers given. Thank you.