PC halts on blank screen with flashing cursor, happened after update.

So an update, both systems were 32bit! I hadn't known this off the cuff, why there was 8gb of ram is unknown to me on a 32bit system. Anyway! So using the 32 bit recovery environment for windows 10 i was able to access system restore, which failed and caused some kind of hdd corruption. So i restarted back into the recovery environment again and launched cmd and ran a chkdsk on the now corrupted partition. Had a variety of problems and repaired them. So I started the system restore and tried an older recovery date and its taking a while. So I'll keep you posted once it finishes.

System restore didn't work and now it claims I have no restore points. HDD seems ok, data still on there. Tried 'roll back build', didnt work, It lists windows 10 as the roll back build, so i imagine there was a build update maybe. I wonder if an offline SFC will work? I will try and SFC /scannow /offbootdir=C:\ /offwindir=E:\Windows
All hope seems lost in the roll back restore department. At this point I'm hoping there is a way to uninstall the potentially bad update. Thanks in advance.

At this point I'm debating resetting this unit. Nothing is working. Hopefully someone can help shed some light on this issue. thanks.

Didn't we just have a cumulative update? Maybe uninstall the last update.

Slugger said:

Didn't we just have a cumulative update? Maybe uninstall the last update.

Possibly right! But how do i go about doing that? Only access i have is the windows 10 recovery envioronment. Can i do it from cmd prompt?

You could just see if you can grab a windows 10 64bit disc as I am assuming Windows 7 is 64bit as you mentioned. If so then Windows 10 would of been 64bit. I'm not sure 2P get 32bit from. Make a windows 10 64bit DVD and try to run sfc /scannow there. Also, there may be an option to revert there or even try to boot into safe mode.

safe mode on command prompt here:

http://www.tomshardware.com/faq/id-2...e-windows.html

64bit doesnt work right only 32bit works. Only Program Files in C:\ drive no "program files (x64)". Thanks for the link! I'm going to give it a shot.

Awesome! Ran 'DISKPART' in Win 10 RE then ran 'list volume' to find that E: was my windows volume. Changed Dir to E:\ and ran the command 'BCDEDIT /SET {DEFAULT} BOOTMENUPOLICY STANDARD'. Then i restarted and hit F8 to go to safe mode with command prompt. typed 'explorer' to start explorer and headed to 'programs and features' 2 updates were listed c++ redist and AMD Catalyst. I couldn't remove them without 'windows installer'.
so i ran

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"

from cmd
and then

net start msiserver

uninstalled both C++ and AMD Catalyst as they were part of the same package i believe. Then Restarted! Then How about it it, we had the same problem. So I had a feeling I was close to a solution so I went ahead and checked the windows update history. (ctrl+x > Control Panel > installed updates) only 1 update had been loaded recently. KB3093266. So i removed it and rebooted the computer... again. Same issue persisted. So what if it was related to the driver but the driver hadn't actually removed the video driver yet.... so i jumped back into safemode yet again. crtl + x > Dev Manager. Rolled back video driver, then rebooted... FANTASTIC!!! It WORKED!!! so there is a link between the AMD Video Driver and the no boot. I think you could probably skip all of those steps and just roll back the video driver. But so far it is a huge success!!! Thanks GamerwGlasses

for the link it really helped the cause!!!

Update your My System Specs.
What AMD graphics card are you using?