What does a repair technician do when Windows will not boot?

What happened before the failure?

We ask when the PC last started normally and what changed afterwards. An update, power loss, driver change or stop code can point us towards the right checks. A photo of the screen is often useful too: No boot device, a blue screen and a failed update point to different stages of startup.

Data matters as well. If important files exist only on this SSD, protecting them may take priority over repairing Windows.

Is it safe to work on the installation?

A failing or unstable SSD can cause startup problems. If the drive disappears during reads or reports errors, avoid intensive writes to Windows and protect the data first.

If the Windows volume is protected with BitLocker, the recovery key may be required to access files and logs. Knowing whether there is a usable backup and whether that key is available helps us decide how to proceed.

Where does startup stop?

The last visible stage of startup determines which checks are useful. These symptoms guide the investigation; none identifies a single cause on its own.

No normal hardware start

If there is no normal logo or display, check power, motherboard, memory, video output and connected devices first.

‘No boot device’ or the SSD is missing

Check whether the drive is detected and whether Windows Boot Manager and the boot files are still present.

The Windows logo appears and then startup fails

Windows has already started loading. Updates, early drivers, damaged Windows components and storage faults become relevant.

The sign-in screen appears but the desktop does not work

Then user profiles, applications, security software and components that start later in the Windows session may be involved.

If Windows itself cannot start reliably

The installation on disk can be examined from Windows Recovery Environment or another recovery environment. Windows does not have to boot normally first.

Checks can include:

• which updates Windows records as installed or incomplete;
• whether Windows components are damaged;
• which drivers load early;
• whether the boot files are intact;
• which errors appear in the logs.

From diagnosis to an agreed repair

On a simple PC with a good backup and known software, reinstalling may be faster than tracing a software fault.

On a work PC, we first check what would have to be rebuilt: an accounting package, certificate, scanner profile, VPN, local database or old licence can add significant work. Repairing the existing installation may save that reconfiguration.

At Forcys, diagnosis is followed by advice and a price indication. We carry out the repair after approval, then test the result. This gives you a chance to weigh the proposed repair against what is needed to use the PC again.

How is the repair tested?

We restart the PC more than once. An update can continue configuring during a later boot, and a driver fault may return only when the normal software stack is active.

On a business workstation, we also test the applications, printers, mapped drives and other functions the user has identified as important.

For technical self-help, continue with the Windows recovery knowledge base.