Applies To: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials
-->
This topic contains troubleshooting guidance for issues that you might encounter when you connect a computer to the server that is running Windows Server Essentials or Windows Server Essentials.
Note
For the most current troubleshooting information from the Windows Server Essentials and Windows Server Essentials community, we suggest that you visit the Windows Server Essentials Forum. The Windows Server Essentials Forum is a great place to search for help, or to ask a question.
This topic provides solutions for the following issues:
Issue 1![]()
Issue
I get a Package installation did not succeed. Try to install the Windows Server Essentials Connector again. If the issue persists, contact your network administrator error when connecting a computer to the server
![]()
Description
This issue may occur if you connect a computer to a server that is running Windows Server Essentials while other Windows updates or application installations are pending and the Connector installation is canceled.
Solution
Complete all other updates or application installations. Restart the computers if prompted.
Issue 2
Issue
Cannot join a computer to Windows Server Essentials
Description
Computers that have non-ASCII characters in the computer name cannot be joined to Windows Server Essentials. If the computer name includes non-ASCII characters, you receive the error message 'An unexpected error has occurred.'
Solution
Rename your client computer with a name that contains ASCII characters only, and try to add the computer to Windows Server Essentials again.
Issue 3
Issue
I get a The Connector software installation is canceled error when connecting a computer to the server
Description
To be able to connect a computer to the server, the SYSTEM account must have Full Control permissions on server folders displayed on the Windows Server Essentials Dashboard. If the required permissions have not been granted, you receive the 'The Connector software installation is canceled' error message.
Solution
Grant the SYSTEM account Full control permissions on each server folder.
To grant the SYSTEM account Full control permissions on a server folder
Issue 4
Issue
I get a To run this application, you must install one of the following versions of the .NET Framework: V4.5.50709' error when connecting a computer to the server
Description
When you connect a computer to a server that is running Windows Server Essentials or Windows Server Essentials, the wizard attempts to install .NET Framework version 4.5.50709 on the computer. However, if an earlier release of .NET Framework version 4.5 is present, the updated release cannot be installed, and the connection attempt fails with this error message: To run this application, you must install one of the following versions of the .NET Framework: V4.5.50709. Contact your allocation publisher for instructions about obtaining the appropriate version of the .NET Framework.
Solution
Uninstall .NET Framework 4.5 from the computer, and then connect the computer to the server.
To uninstall .NET Framework 4.5
Issue 5
Issue
I get a The server is not available. To resolve this issue, contact the person responsible for your network. error when connecting a computer to the server
Description
This can happen if the date and time on the connected computer are not synchronized with the date and time on the server. Windows Server Essentials and Windows Server Essentials use the time synchronization service to synchronize the date and time of computers running in a Windows Server Essentials or Windows Server Essentials network. Synchronized time is critical because the default authentication protocol uses server time as part of the authentication process. For example, if the clock on a client computer is not synchronized to the correct date and time, Windows Server Essentials or Windows Server Essentials authentication might falsely interpret a logon request as an intrusion attempt and deny access to the user.
This can happen if the server's free memory is less than 5 percent.
This can happen if you already have a VPN connection to the Windows Essentials Server and you try to configure the Connector software off-premise by using a domain address.
Solution
To change the date and time on the client computer
To change the date and time on the server
Issue 6
Issue
I get an An unexpected error has occurred. To resolve this issue, contact the person responsible for your network. error when connecting a computer to the server
Description
If you receive this error message, the WSS Certificate Web Service might not be running.
Solution
Start the WSS Certificate Web Service.
To start the WSS Certificate Web Service
Issue 7
Issue
When I try to connect a computer to the server again after an unsuccessful connection attempt, I receive the warning A computer with this name is already connected to the server
Description
If an earlier attempt to connect a computer to the server was canceled or interrupted, you might receive the following warning when you try to connect again: A computer with this name is already connected to the server. This happens because a certificate was issued when you tried to connect to the server the first time.
Solution If you are sure that no other computer with the same name is already connected to the server, click Next, and then follow instructions to complete the Connect my computer to the server wizard.
Issue 8
Issue
When I attempt to connect a client computer that is running Windows 7 Home to the server, the web page for running the connector software opens, but the client computer cannot connect to the server
Description
If the router on your network has multicast enabled, communications between the server and a client computer running Windows 7 Home Basic or Windows 7 Home Premium do not work correctly.
Solution
Disable multicast on your router. On some routers, that might include disabling the RIP-2M routing protocol. For more information, refer to the documentation provided by the router manufacturer.
Issue 9
Issue
Auto logon stopped working after I connected the computer to the server
Description
If auto logon is set for the user account when you connect the computer to Windows Server Essentials, the setting is overwritten when the connector software is installed on the computer.
Solution To resolve this issue, when you connect the computer to the server, note the password that is used for the user account. After the connector software is installed, configure auto logon to use that account.
Note
The Windows Server Essentials domain account requires a password that meets the default password policy requirements.
Issue 10
Issue
Uninstalling a prerelease version of the connector software does not remove existing logs
Description
After you update from a pre-release (Beta or RC) version of Windows Server Essentials to the released version, you must remove the connector software from each computer that was connected to the server, and then connect the computer again to install the released version of the connector software.
However, when you remove the connector software from a network computer, the existing log files in the %ProgramData%MicrosoftWindows ServerLogs folder on that computer are not deleted. If you do not delete the Logs folder, the log files can become corrupt when you connect the computer to the released version of Windows Server Essentials.
Solution To avoid corruption of the log files, manually delete the Logs folder before you reconnect the client computer to the updated server.
To reconnect a computer after a server update without corrupting the log files
Issue 11
Issue
I want to upgrade the operating system on a client computer
Description
During the installation of the connector software, numerous checks are performed against the client operating system to ensure the client meets all the connector prerequisites. If you upgrade the client operating system after you install the connector software, some of the prerequisites might not be present, and the client connector might fail.
Solution
Before you upgrade your client operating system to a different version (for example, you upgrade Windows XP to Windows Vista or Windows Vista to Windows 7), you should uninstall the connector software. Use Add or remove programs in Control Panel. After the client operating system upgrade is complete, you can reinstall the client connector by opening http://<server>/connect in a Web browser, where <server> is the name of the Windows Server Essentials server.
If you have already upgraded the client with the connector software installed, use Add/Remove Programs or Programs and Features to uninstall the connector software. Then install the connector software again.
See also
Windows 7 is designed for networking and working with the Internet, so when your network connection isn’t working, it can be particularly frustrating. Fortunately, Windows 7 comes with a built-in troubleshooter that you can use to repair a broken network connection.
Sometimes the troubleshooter isn’t able to correct the problem. In that case, it’s best to delete the connection and just create it again by clicking the Setup a New Connection or Network link in the Network and Sharing Center window and entering the correct settings.
Summary :
Windows 7 stuck at loading screen and never pass through? Even though a reboot is not useful? Here we list some solutions to Windows 7 hangs at start logo for you to have a try.
Quick Navigation :Overview of Windows 7
Released on Oct. 22, 2009, Windows 7 has gone through nearly 10 years. Despite the fact that Microsoft had officially announced the end of support to Windows 7 by Jan. 14 2020, a great number of users are sticking to use Windows 7.
Why? The reason is that Windows 7 runs stable and is easy to operate. Most important of all, users have got accustomed to operating Windows 7 rather than the else.
Although Windows 7 is still enjoying great popularity, it is not a 100% perfect system. Users often encounter kinds of issues during the operation, such as Windows 7 stuck at loading screen, Windows Could Not Format a Partition Error Code 0x80070057, can't access a partition in Windows, and so on.
Since we have already discussed the latter two situations, today we are going to talk about the first one: Why Windows 7 stuck at loading screen and how to fix it.
Help! My Windows 7 stuck at Loading Screen…
A rather frustrating thing is that when you start Windows 7, it hangs at the start logo, and the time may last from minutes to hours, depending on why Windows could not start correctly.
In this situation, you may set it aside and do something else, only to find it keep freezing there when you come back; or you may force the computer to shut down and restart Windows 7, only to find Windows 7 is freezing on startup again and again.
This situation is not rare and you are not alone in fury. Many Windows 7 users have the same experience.
Yesterday I woke up to my computer sitting at the starting windows loading screen. I have no idea why it turned off but now every time I try to start it, it sits at the loading screen. Please, someone help! Tomshardware
So, the question here is: what should you do when Windows 7 stuck at loading screen? We believe there are many suggestions mentioned on the internet to cope with this problem, however, you have no idea whether they are credible or not. With that in mind, we have filtered feasible solutions for users to refer to.
10 Solutions to Window 7 Freezing on Startup
Note: There is a possibility that some methods listed here won’t help you to fix the problem, but they are indeed useful for other users. So please keep trying them out one by one, hoping all of you good luck.
Here are 10 solutions if your Windows 7 hangs at start logo:
Solution 1. Start Windows 7 in Safe Mode and then Restart Windows Normally
Start Windows in Safe Mode, and then restart your computer as usual. Yes, you read that right, just start Windows 7 in Safe Mode and then restart your computer without doing anything in Safe Mode.
The reason for doing so is that sometimes Windows updates or something else gets hung up. In this case, a forced restart won't get work. But if you try it from Safe Mode, miracle happens sometimes.
However, if this doesn't work, try the following ways.
Solution 2. Do System Repair by Using Windows 7 Installation CD
You can try repairing system with Windows 7 installation CD: press Shift+F10 to bring up the command prompt window. In the command prompt window, run bootrec.exe. This should be helpful.
Parameters for bootrec.exe are:
Or you can also do like this: Insert the Windows installation CD. Then it will load drivers and the screen should pop up to go on installing Windows. but on the lower left corner you can see the option Repair your computer. Click that option and it should fix the problem.
Solution 3. Try System Restore
If you have made full system backups in daily usage, things will become very easy. You can restore the system to a time when it works.
Step 1. Start Windows 7 normally. Before you see the Windows loading logo, press F8 on your keyboard. Then you can see a variety of Advanced Boot Options.
Step 2. Choose Repair Your Computer and wait until Windows 7 repair mode is ready.
Step 3. If you are told to choose keyboard, just click OK. If you are told to choose an account, choose your account, and click OK. If you have set password for your Windows account, enter the password too. Then you can see System Recovery Options.
Step 4. Choose System Restore.
Step 5. Here you can see all Windows restore points available. Try your best to recall when your computer is safe and sound, and choose the corresponding restore point. If you do not see the full restore points, check Show more restore points.
Step 6. Click Next. It will try restoring your Windows to the restore point you have selected. This will take some time before the system restore is done.
Solution 4. Try Checking & Fixing Hard Drive Errors
If System Restore did not work or failed, there is one more thing you can have a try - CHKDSK. Hope this helps.
Step 1. Turn on your computer, and before you see the Windows loading logo, rapidly press F8 key on your keyboard. Then you can see a variety of Advanced Boot Options.
Step 2. Choose Repair Your Computer and wait until Windows 7 repair mode is started.
Step 3. If it asks you to choose a keyboard, just click OK. If it tells you to choose an account, choose your account, and click OK. If you do have password for your Windows account, you need to enter it too.
Step 4. Now, you will see System Recovery Options.
Step 5. Choose Command Prompt, this will run Windows command prompt. When you see the black command shell, type chkdsk /f. This will scan your hard drive for errors, and will try to fix the errors if it detects any. Also, you can type chkdsk /r to scan and try to repair bad sectors. This process can take some time so please wait until the disk check is done.
Step 6. Restart your computer.
However, if the same situation happens, this means there is a certain issue for the hard drive. Then you should consider replacing it. If you decide to do so, use the Copy Disk feature of MiniTool Partition Wizard Bootable CD to clone hard drive.
Tip: MiniTool Partition Wizard Bootable CD is a highlighted feature available in all paid editions of MiniTool Partition Wizard. If you have no paid edition at hand, you can press the button below to get the Pro Edition at a good price.
Please select Bootable Media on the toolbar and follow How to Create Bootable Partition Manager to create a bootable CD/DVD disk or USB flash drive. Then set computer to boot from the bootable media in BIOS. After that, copy the whole disk to another one. In this way, you won't lose any data in the source disk if anything bad happens.
To be specific, follow the steps below:
Step 1: On the main interface of MiniTool Partition Wizard, right-click the Windows 7 system disk to be cloned and choose Copy Disk.
Step 2: Choose a target disk to hold all content of the source disk. Note that all data on the target disk will be cleaned so be sure that this drive can be cleaned or a backup has been made in advance.
Step 3: Choose a copy option here. You can keep the original partition size, keep the proportion of the partition sizes, or customize the partition size of each partition. Besides, here are two options for you:
Check 'Align partitions to 1MB' to improve the performance for Advance Format disk or SSD.
Use 'GUID Partition Table for the target disk' to support disk larger than 2TB.
Step 4: Go through the next message telling how to boot from the target disk until you reach back to the main interface. Finally, click 'Apply' to carry out this change.
With this disk copy at hand, you don't have to worry about data loss caused by Windows 7 stuck at loading screen or other issues.
See also:Fix Windows Stuck at Loading Files
Solution 5. Check CMOS and CMOS Battery
This includes two aspects, the CMOS and the CMOS battery. CMOS is a read/write parallel or serial flash chip on the motherboard, and is used to store the hardware configuration as well as user settings.
To clear the CMOS, clear the BIOS memory on your motherboard. And the easiest way is to remove the CMOS battery for a few minutes. This will revert the BIOS settings to the factory default levels. A BIOS misconfiguration might be the reason that Windows is freezing during startup.
A CMOS battery that is out of charge for long time can certainly be the cause of Windows 7 freezing on startup. Replace the CMOS battery if your computer is more than two or three years old or if you have shelved the computer for a long period of time without usage.
Solution 6. Check System RAM
Maybe there is a problem with your system RAM. Sometimes, when your computer memory is bad or when a memory slot on computer motherboard is bad, Window 7 freezing on startup could happen, but this is rare.
Try changing your computer memory or reinstalling the computer memory. After that, restart the computer in Safe Mode. In Safe Mode, press Win + R keys to run MSCONFIG and press OK. Here please select the clean boot option by unchecking all the options under Selective Startup. Finally, press Apply and restart Windows 7 in normal mode.
Solution 7. Remove Video Card Driver
In rare cases, Windows 7 hangs at start logo could be caused by your damaged video card driver. Try booting into Safe Mode and remove it. After that, reinstall the video card driver. Now restart Windows 7 and see if you can boot into normal mode.
Solution 8. Scan Your Computer for Viruses in Safe Mode
Scan your computer for viruses in Safe Mode. A virus or other kind of malware might have caused a serious problem in Windows, preventing it from starting up properly. Since most viruses and malwares cannot be loaded under Safe Mode, this could return you a clean Windows 7.
Tip: If you can't get to Safe Mode, you can still scan for viruses using a bootable malware scanner.
Solution 9. Uninstall Antivirus Software
If it is not viruses then it may be your antivirus software. The conflict between your antivirus software and Windows 7 may cause Window 7 freezing on startup. Many users explain that when they uninstalled their antivirus software under Safe Mode, everything becomes fine.
Solution 10. Reinstall Windows 7
The last and also the most direct way for Windows 7 stuck at loading screen is to reinstall Windows 7. However, a critical defect is that you will lose all data in system partition, including the operating system, the applications and other files you put there.
So, this is not recommended unless you have no other choice. But if you are forced to do so, try using MiniTool Partition Wizard Bootable to recover files you need in the system partition before reinstalling Windows 7.
Usually, you can the Data Recovery feature to recover needed files or try using Copy Partition feature to back up the whole system partition. Both will prevent data loss to the largest extent.
Verdict
Windows 7 stuck at loading screen is often bothering Windows 7 users, making them annoying so much. In this post, we have listed 10 available solutions and we hope you will find at least one of them useful.
Next time when your Windows 7 hangs at start logo, try these solutions one by one. If you find them beneficial, share with your friends; and if you have any additional tips to add, be sure to let us know!
Windows Media Player 12 relies on its configuration settings in order to run smoothly. Not only are there settings just for the program to use, but also custom ones that are saved when you make a change — like customizing the view or adding music folders.
However, things can go wrong with these configuration scripts. Usually, corruption is the reason why you suddenly get a problem in Windows Media Player 12. For instance, when you run the program, a problem might arise such as:
Diagnostic Troubleshooting Wizard Windows 7
If you've got a stubborn configuration problem in Windows Media Player 12 that you can't seem to fix, then instead of uninstalling WMP 12 and starting again, then all that you might need to do is reset back to its default settings.
One of the best tools to use for this job is actually already built into Windows 7 (or higher). It's called MSDT (Microsoft Support Diagnostic Tool). It will detect any corrupt settings in WMP 12 and can be used to reset them back to the original settings. To discover how to do this, follow the simple tutorial below.
Running the MSDT Tool
Normal Mode
If you have chosen to run the MSDT tool in the default mode, then you'll have 2 options.
Advanced Mode
Windows 7 Troubleshooting Wizard Not Working On Pc
If you've got problems with the music library in Windows Media Player, then you might want to read about rebuilding WMP's database.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |