Windows 10 boot problems

Topic

New Reply

All these systems have had Windows 10 installed for about 3 months.
I have had 8 different systems that would not boot up saying that Windows needed to be repaired.
In all cases I would boot from my Windows installation CD and tell it to repair my Windows.
Each time after running for a short time it would come back and say it could not fix Windows.
However after that Windows would boot up and work.
Whatever Microsoft could not fix seemed to correct the problem.
Things that are common to all systems are:
They are all older system that were upgraded from Windows 7.
Updates were involved because all had to finish installing updates during their boot up.
All had been shut down for the night or because storms were in the area.

Is this a known problem?
Has anyone else seen this problem?
Is there a fix for it?
I think Microsoft may want to redo the way they handle shutdowns when updates are involved.

Reply | Quote

Replies

You might want to consider a clean reinstall of Windows 10 on one of the systems after making a complete backup of it.

--Joe

Reply | Quote

Yes I have though about doing a fresh install and I may if I get any more failures.
The problem is that 5 of the systems are in doctors offices and a fresh install would require a 3rd party to remotely reinstall their application.
I will wait for a repeat failure on one before getting serious about a fresh install.

Reply | Quote

I’d select one system under my control. That way it can be done when needed and tested as much as needed to ensure it is fixed.

--Joe

Reply | Quote

My problem is, they are all client systems.

Reply | Quote

Can you read the Event Logs on those machines to see what Windows thinks is the issue?

cheers, Paul

Reply | Quote

The event log for the most resent one shows that updates were in progress when the system was shutdown.
When I questioned the client he said when he told windows to shutdown,
he was ask to shutdown or install updates and shutdown.
He chose shutdown. It looks like Windows should not give that option.
I think the message should be ” updates are in progress, shutdown will happen after they finish” or something like that.

I tried to upload the event file, but that turned into a bad experience, could not get the upload to work.

Reply | Quote

A couple of questions:

1. Did they have a good backup from before the upgrade to Windows 10?
2. Why did they upgrade mission-critical working Windows 7 computers to Windows 10?

From the way everything is described, it sounds like Microsoft pushed Windows 10 to their machines and upgraded them, rather than them making the decision to upgrade.

Unless you have a good backup that you can restore from, then I’m with Joe, your best way to clean up the mess on these computers is to do a clean install. Windows 7 or 10. And make sure there is a good backup after the reinstall.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote

1) Except for a couple of home users that did their own up grades all had fresh system images backups.
2) Home users make their own choice about upgrading.
My business clients all had a mixture of Windows 7, 8.1 and 10.
They made the choice to upgrade so that all systems had the same OS.
For one customer, their application vendor wanted as many of their clients as could off 8.1 and on 10.

Reply | Quote

Why would the app vendor want to move from 8 to 10? There isn’t anything in 10 that an app needs.

cheers, Paul

Reply | Quote

Paul, I do not have your answer, except that they were wanting to get away from 8.1

Reply | Quote

If the vendor wanted them on 10, then I’m sure that the vendor will be glad to remotely reinstall the applications.

Group "L" (Linux Mint)
with Windows 10 running in a remote session on my file server

Reply | Quote