Skip to main content

How to solve Windows 7 Libraries folder keeps opening or popping up at startup?

Sometime you have to use Upgrade Option for your Windows 7 system to do repair.
In that case, you will encounter Windows Libraries Explorer is keep opening or popping up at startup after you did repair with Upgrade option.

To solve this error, please follow below steps,
Open registry editor and go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Winlogon

Check the value of Userinit and you will notice two userinit.exe like this " C:\Windows\system32\userinit.exe,C:\Windows\SysWOW64\userinit.exe, ".

You have to delete one of that to solve the error.

You can choose which one to delete depends on your Windows 7 version, 32 bit or 64 bit.

64-bit versions = C:\Windows\system32\userinit.exe
32-bit versions = C:\Windows\SysWOW64\userinit.exe

But for the best, choose "C:\Windows\system32\userinit.exe" as default and delete "C:\Windows\SysWOW64\userinit.exe".

OK. Now your Libraries folder will not pop up at startup. Error resolved.

But take note the above steps are need to modify the registry. So that you better backup the registry before you edit. By doing this you can restore registry back if something goes wrong.




May you all be happy.
( Be knowledgeable, pass it on then)

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. services.sh restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f