Wiki Home Boot Issues Client stops booting at the Windows logo
Client stops booting at the Windows logo
When the client boots, if it always stops at Windows Logo, and no longer reads data from the server, you can find some causes and solutions below.
- The client NIC driver is not proper. You can install the latest NIC driver before uploading the image (You can download the latest NIC driver from the respective vendor’s website). Sometimes you need to install the "RISC" type driver of the NIC (such as NVIDIA and BROADCOM).
- The client IP is in conflict with other LAN IP addresses. You can re-assign another IP to the client.
- Some smart switches have IP-MAC binding functions. You can cancel the switch IP-MAC binding or rebind all machines IP and MAC addresses.
- When the hard disk installed machine boots diskless, then error occurs. Solution: Remove the hard disk or disable HDD on BIOS.
- If the operating system of the client is Windows 7 x64, before installing CCBoot Client, please install the Windows latest updates even if your system is already installed SP1.
- In CCBoot Cloud CP click the "DHCP" tab, and then click the "Scan DHCP" button to check whether there are other DHCP services on the LAN, if so, please disable other DHCP service, especially in the router.
- When you use different switches, some can diskless boot successfully, some stops at Windows Logo when booting, you can try to change the PXE value from "gpxe.pxe" to "ipxe.pxe" in "Edit Client" modal.
- If you have a wireless card or multiple NICs, just leave the NIC used to boot from LAN, and disable the other NICs in Device Manager before installing CCBoot client, and then upload the image.
- Sometimes, some billing softwares, filter softwares, Windows firewall and antivirus software etc. may also cause diskless boot failure. We have tested the following softwares, and they work with CCBoot successfully. If your software is not in the following list, you can send an email to email@example.com, tell us your software, let us check it and find a solution.
CCBoot works with these billing softwares: CafeSuite, SmartLaunch, CyberCafePro, Handy Cafe, Pinoy Big Timer, Easy Cafe, Antamedia, EZ Timebilling, PC Time Logger, Timer Professional, CMS and Truecafe etc.
CCBoot works with these filter softwares: TRedFilterCafe and WinpkFilter (For details, please refer to "TRedFilterCafe and WinpkFilter").
- The ARP driver has been installed. Solution: Remove the installed ARP driver.
- If the client gets IP from a third party DHCP, sometimes, you cannot boot it. Windows 7 creates an explicit route to your iSCSI target using your default gateway. This means if your target is on the same LAN, your router must be prepared to route local LAN traffic (which normally it would not do as the initiator and target could communicate directly). Some strict firewall settings or router will prevent this kind of routing which will cause Windows 7 booting failure. For example, using Shorewall you need to enable the "routeback" setting on the LAN interface. If using OpenWrt (without shorewall) add this to /etc/firewall.user (create this file if absent):
iptables -A forwarding_lan -i br-lan -o br-lan -j ACCEPT
Another solution: Don't set a gateway on the third party DHCP, and just set a gateway in the CCBoot client properties. It may be the memory connection problem, please take the memory out and clean it.
If you have installed an Antivirus program on the server, it can cause the client to stop booting and get stuck at the logo as well. So, to fix it, you have to uninstall the antivirus programs.
- If you are using a newer motherboard - z370 chipset boards with Realtek NIC, then you may also get stuck at the logo. To fix it,
- You have to install NIC drivers from Realtek’s website and do not use Microsoft installed drivers.
- When you install CCBoot Client in the OS before uploading an image, do not click the "Yes" button when it asks to optimize Windows.