Windows 10: Failed Reverting Back to 7

That just says they put Windows 7 Pro on it. Doesn't say it is retail. Why couldn't the company be using volume licensing?

Wait - a volume license pprobably wouldn't be prompting for the normal upgrade to Windows 10 - so you are probably correct. Unless the company was violating EULAs and using OEM versions.

Or is it just the actual enterprise versions that won't prompt for upgrading? Hell, I don't know, now I've gone and confused myself!

 

Say all you want.
That is what I believe in.
This is also my last time responding to you. You like to show off your "computer prowess" by picking on others, that's you entertainment.
I won't be part of it.
Your future replies will be ignored.

 

Should the revert work if it is a volume license?

One item to note, when in win 10, there was an issue with HP Security software. So I started to uninstall the security software. I had to uninstall around 5 or 6 components separately. For the last one, it did not finish (was hanging for 20 min) so I canceled it. On next boot, Sign in hung with a message from the HP software (i do not recall). After around 60 seconds it said it could not find the finger print reader (or something like that). Also, the system had two user accounts so on the bottom left, instead of listing the names, it just listed password where the account name would be. At that point, I decided to revert thinking it would be no big deal.

I wonder if the security software did not allow windows to boot on the revert. It failed on the first boot of the revert process.

 

It's hard to tell exactly what happened. Sounds like a whole bunch of different things went wrong, so probably the only recovery is going to be a clean install (or image restoration) of Windows 7.

 

Please post back the final result.
And if the issue is resolved, I would like to know what method used.
Thank you.

 

If it is a company computer, I would just let their IT staff take care of it. Every IT department has their own methods, settings, configurations, etc.

 

we just re-imaged the drive. was not worth trying to fix.