Table of Contents
**__Windows 10__**
**__Windows 7__**
- 2011-05-03
How to Stop sidebar.exe Using Lots of Memory Posted on March 7, 2011 by Brendan in Windows One of my readers, TED has made a suggestion as to a hack fix to the sidebar.exe memory problem (as documented in my blog post Windows sidebar.exe Memory Leak). With some spare time at the moment, I’ve been able to implement his suggestion and confirm it works. I’ve written a batch script, and confirmed this works in Windows 7 (should work in Windows Vista too). I created a batch file called restart-sidebar.bat, and stored it in c:usersbrendan – contents of the file below: @echo off taskkill /im sidebar.exe /f echo This script will now sleep momentarily… TIMEOUT /T 2 echo Starting sidebar.exe now… start sidebar.exe The idea is it will kill the process called / task with the image name of, sidebar.exe, forcefully. It will then wait two seconds before starting the process again. To complete the setup, create a new scheduled task specifying the path to your newly created batch file (mine was c:usersbrendanrestart-sidebar.bat). Run the scheduled task as your own user. I have it scheduled to run once a day at 5pm. I prefer to have it run when I’m not using the computer, more of a scheduled maintenance task that goes on behind the scenes. If you find that’s not enough, schedule it to run a few times a day. For your information – I’ve encountered on only a few occurrences problems in the past when shutting. The sidebar process has stalled the shutdown procedure and Windows has forcefully killed the process. On login again I’ve lost a few sidebar settings. While I’ve not encountered this running the above batch script, it’s possible you may encounter this. If you’re concerned about it, drop the /f from the taskkill line in the above script (as to not force it) and increase the timeout value from 2, to up to 20 seconds to allow it to safely exit. Downsides / Cons - I haven’t been able to find something to force the batch file to run in a minimised window (so it pops up and runs as a black command prompt window). This I’m a little bit disappointed with – you could perhaps create a shortcut to the batch file and set the properties on it to start minimised – however I’ve not confirmed this works. Advantages / Pluses - It’s a simple and easy fix. Avoids the pain of closing all your programs and restarting / logging off. Runs in seconds and doesn’t require administrative privileges to run.
**__Windows Vista__**
- Enable Remote Desktop in Windows Vista Home Premium | Welcome to Andrewblock.net - Learn how to enable remote desktop in Windows Vista Home Premium with a simple registry file.
- enable remote desktop on Windows Vista Home Premium | Welcome to Andrewblock.net - How to enable remote desktop connection on vista home premium x64 & x86
**__Windows XP__**
WINDOWS XP SHUTDOWN & RESTART TROUBLESHOOTING
- 4 Ways To Shutdown/Restart The System At A Specific Time In Windows | Technize - Be Techdated
Shares Access Denied & IRPStackSize
shares problems can be solved by the method of “increase the IRPStackSize value in the registry” if your event viewer mentions it!
- Run regedit.
- Navigate to the following key:
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesLanmanServerParameters
- In the right pane, double-click the IRPStackSize value.
NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
a. In the Parameters folder of the registry, right-click the right pane. b. Point to New, and then click DWord Value. c. Type IRPStackSize. IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive. - Change the Base to decimal. - In the Value Data box, type a value that is larger than the value that is listed.
If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK.
- Close the Registry Editor and restart the computer.
If the problem persists after you complete the preceding procedure, try to increase the value of IRPStackSize even more. The maximum value for Windows 2000 is 50 (0x32 hex).
If you are running Windows NT 4.0, and the problem persists after you complete the preceding procedure, you may have to apply Windows NT Service Pack 4 or Service Pack 5.
HID Input Service failed to start
Event Viewer: Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7023 Date: 22/12/2007 Time: 1:25:00 PM User: N/A Computer: WDGC Description: The HID Input Service service terminated with the following error: The system cannot find the file specified.
The following could be a solution
- “Start”, then “Run”
- Type “regedit” without the quotes, click “OK”
- Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentC ontrolSetServicesHidServParameters
- In the right pane, right-click in the blank area and select “New” and “Expandable String Value”
- Name the value “ServiceDll” without the quotes. Note: it is spelled S E R V I C E D L L but you enter it exactly as shown between the quotation marks.
- Double-click the new entry and enter “%SystemRoot%System32hidserv.dll” without quotes as its value
- Click OK, and close the registry window
Exclamation Reboot.
If you are reluctant to make manual registry edits, the following will make the registry change for you:
Using your mouse, Highlight the entire contents of the code box below, including any blank lines. Then do a Right-click | “Copy”:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHidServParameters] "ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f, 00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00, 68,00,69,00,64,00,73,00,65,00,72,00,76,00,2e,00,64,00,6c,00,6c,00,00,00
Open a new Notepad session. Click Format and make certain that Word Wrap is disabled. Do a Right-click | “Paste” of the code box contents. Click File, click “Save as…” and enter as the filename (including quotation marks): “c:\fix_regs.reg”.
Exit Notepad. Double click your new file, fix_regs.reg[/b] and agree to the registry merge when asked. Reboot.
SHUTDOWN WORKS, BUT IT’S REAL SLOW
- If it appears that Win XP is not shutting down, give it some time. Some users report a minute or longer for shutdown to visibly start. Generally, this is a consequence of software that is running when shutdown is attempted. It also may have something to do with particular hardware. If you experience this problem, be sure to close all running programs before attempting shutdown and see if this solves your problem. If so, then you can determine, by trial and error, which program(s) are involved.
- Newsgroup correspondent “Sarah” provided one specific solution for this. In Control Panel | Administrative Tools | Services, stop the Nvidia Driver Helper service. (You can also get this by launching SERVICES.MSC from a Run box.) Many other newsgroup participants quickly confirmed that this solved this “extremely slow shutdown” problem for them (it’s the most successful solution for this problem to date). According to correspondent Gan Ming Teik, downloading and installing the new version 23.11 Nvidia driver also solves this problem.
- Correspondent Ron Spruell found that disabling the Terminal Services service reduced his shutdown time from over 2 minutes (hanging at the “Windows is shutting down” screen) to about 10 seconds. To disable Terminal Services, follow the steps in the prior paragraph for launching SERVICES.MSC. Please note that Terminal Services is required in Windows XP for running Remote Assistance, Fast User Switching, and (in XP Pro) Remote Desktop.
- Correspondent Graeme J.W. Smith reported a more obscure cause of slow shutdown: In Win XP Professional, the Group Policy Editor has a security option to clear the pagefile at system shutdown. The same setting also forces the hibernation file to be wiped at shutdown. These processes take long enough that users may think that shutdown has hung. To change the setting, click Start | Run, type GPEDIT.MSC, click OK. Drill down to Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options. In the right pane, find “Shutdown: Clear virtual memory pagefile.” NOTE: Since someone actually has to have set this policy, the problem will be pretty rare, but is worth mentioning. However, Forum participant “roadrunner” reported that the personal security app Privacy Eraser automatically enables “Clear virtual memory pagefile,” and, therefore, may be the cause of a slow shutdown.
- The Gear Software Security Service (GEARSEC.EXE), which enables iTunes for Windows to read and burn CDs, has been reported by many users to cause Windows XP to hang at the “Windows is shutting down” screen for as long as 20-30 seconds. WORK-AROUND: Stop the service prior to shutdown. One way to to this (suggested by “Thornburgh”) is to create a batch file with the one line net stop gearsecurity. You can either launch this batch file manually, or (in Win XP Professional) use GPEDIT.MSC) to specify this batch file as the shutdown script (under Computer Configuration | Windows Settings | Scripts | Shutdown). Gear Software’s forum has a thread on this issue here. (Tip from correspondent “Andy”)
- MS-MVP Gary Thorn discovered that the Event Log can slow down Win XP shutdown. Disabling event logging removed the slowdown. If this works for you, then the real troubleshooting begins: finding out, by trial and error, what item that is being logged is causing the actual slowdown. (In Gary’s case, the Telephony service was causing the problem.) To disable the Event Log, launch the Services console as detailed in No. 2 above, and disable Event Log (right-click on Event Log, click Properties, under Startup Type select “Disabled”).
- In a domain environment, don’t forget to check any logoff scripts you are pushing. These can be a source of slow or hanging shutdown processes. Site visitor Tony Barkdull, for example, found that an enforced logoff script caused show shutdown for laptops that were off-site. He solved it be creating a logoff script on the local machines that deletes the Active Directory logoff group policy after it runs so that the logoff scripts are absent while a user is off-site, but are repopulated when they return. — A related cause of slow shutdowns is offline synchronization of data, which is increasingly common with mobile computing, but is usually much more obvious to the end-user.
How to change Terminal Server's listening port
How to change Terminal Server's listening port
SUMMARY By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To change the default port for all new connections created on the Terminal Server:
1. Run Regedt32 and go to this key:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp NOTE: The above registry key is one path; it has been wrapped for readability.
2. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.
To change the port for a specific connection on the Terminal Server: • Run Regedt32 and go to this key: HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal ServerWinStationsconnection NOTE: The above registry key is one path; it has been wrapped for readability.
3. Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.
NOTE: Because the use of alternate ports has not been fully implemented for Terminal Server 4.0, support will be provided as "reasonable effort" only, and Microsoft may require you to set the port back to 3389, if any problems occur.
To Alter the Port on the Client Side
1. Open Client Connection Manager. 2. On the File menu, click New Connection, and then create the new connection. After running the wizard, you should have a new connection listed there. 3. Making sure that the new connection is highlighted, on the File menu, click Export. Save it as name.cns. 4. Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx is the new port that you specified on Terminal Server. 5. Now import the file back into Client Connection Manager. You may be prompted to overwrite the current one, if it has the same name. Go ahead and overwrite it. You now have a client that has the correct port settings to match your change Terminal Server settings.
Supprimer le dossier de partage du poste de travail
Supprimer le dossier de partage du poste de travail A l'installation de Windows Live Messenger, un “dossier de partage” est créé dans le poste de travail, ce qui permet de partager plusieurs documents avec certains contacts. Pour ceux qui n'utilisent pas cette fonction et qui veulent supprimer cet élément du poste de travail, voici la marche à suivre. Supprimer le dossier de partage
- Faites Démarrer ⇒ Exécuter et tapez regsvr32 -u “%ProgramFiles%\MSN Messenger\fsshext.dll”
- Si cela ne fonctionne pas, allez voir dans le répertoire d'installation de Windows Live Messenger et relevez le nom du fichier de la forme “fsshext.8.x.xxxx.xx.dll”.
o Même opération : Démarrer ⇒ Exécuter et tapez regsvr32 -u “%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll” (en remplaçant par le nom du fichier que vous avez relevé).
Le dossier a disparu ! Rétablir le dossier de partage
- Faites Démarrer ⇒ Exécuter et tapez regsvr32 -c “%ProgramFiles%\MSN Messenger\fsshext.8.x.xxxx.xx.dll” (en remplaçant par le nom du fichier que vous avez relevé, voir ci-dessus).
Le dossier réapparait alors dans le poste de travail.
L'explorateur plus stable !
Astuce performances système : L'explorateur plus stable ! Notre cher Windows gère l’explorateur, le bureau et la barre des tâches au sein d’un seul processus multithreads. Lorsque l’explorateur se fige, c’est alors l’ensemble de la machine qui trinque. Cette astuce permet de lancer l’explorateur au sein d’un autre processus, le bureau et la barre des tâches étant gérés eux via un second processus. Cela permet une plus grande stabilité de la machine, le plantage de l’explorateur ne figeant pas la totalité de l’OS.
Attention tout de même, la création d’un nouveau processus gérant l’explorateur consomme plus de mémoire. Astuce à éviter si votre RAM est insuffisante.
Ouvrir regedit Allez dans HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorer Créez la valeur DWORD DesktopProcess et donnez lui la valeur 1. 0 est la valeur par défaut (les processus ne sont pas séparés).
Windows XP soudainement lent !
Windows XP soudainement lent !
Astuce performances système : Windows XP soudainement lent ! Il peut arriver que Windows devienne lent alors qu’il fonctionnait très bien auparavant. Avant de vouloir réinstaller votre OS, essayez d’appliquer cette astuce !
Attention ! L’utilisation de cette astuce peut dans certains cas créer un plantage complet de la machine ! A utiliser donc en dernier recours avant de passer par un reformatage !
Suite à plusieurs erreurs d'écritures sur le disque sous XP, il se peut qu'au redémarrage suivant, Windows reconnaisse l'IDE principal en mode PIO (au lieu Ultra DMA). Il faut alors désinstaller le pilote dans le gestionnaire de périphérique et redémarrer la machine.
Pour cela, vous devez effectuer la manipulation suivante :
Faire un clic droit sur le Poste de Travail, allez dans Propriétés, Matériel, Gestionnaire de périphériques, Contrôleurs ATA/ATAPI IDE. Faire ensuite un clic droit sur Canal IDE Principal et choisissez Désinstaller. Redémarrer ensuite votre machine.
Ainsi, Windows reconnaîtra à nouveau l’IDE principal en Ultra DMA et non plus en PIO, votre PC retrouvera alors sa vitesse d’exécution d’origine !
Démarrer XP plus vite
Astuce performances système : Démarrer XP plus vite !
Par défaut, XP défragmente les fichiers du boot (utilisés lors du démarrage). Cela permet théoriquement un démarrage plus rapide. Pourtant, si vous avez recours à une défragmentation régulière de vos disques, on se rend compte que cette défragmentation vous fait perdre de précieuses secondes à chaque démarrage.
Cette astuce, pourtant assez connue, peut-être mal utilisée. En effet, nombreuses sont les personnes qui préfèrent activer la défragmentation du boot. Pourtant, si vous utilisez régulièrement un défragmenteur, la défragmentation du boot ralentie alors le démarrage (elle est inutile). La désactivation de cette défragmentation va donc accélérer le démarrage de Windows XP.
Ouvrez regedit (menu Démarrer, Exécuter... et taper regedit) Allez à HKEY_LOCAL_MACHINESOFTWAREMicrosoftDfrgBootOptimizeFunction Modifiez la valeur de la clé Enable à N (Y par défaut) Redémarrer.
Attention : si vous ne pratiquez pas de défragmentation régulière comme indiqué plus haut, il est conseillé de laisser Enable à Y.