Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

W10 - Turned off computer during update now cannot boot into windows


  • Please log in to reply
19 replies to this topic

#1 kateh

kateh

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 03:48 PM

Model:Tosheba Satelite S75T-A7160

OS: Orignally Windows 8.1 OEM upgraded to Win 10 at very end of free upgrade period (unable to get current install verison due to not being able to boot into Windows)

Hardware manufactured: 2014

CPU: i7-4700MQ (2.4GHz)

BIOS Version: 1.6

 

My friend thought his laptop was frozen during a surprise windows update and pressed his power button to turn off his screen and fix it later not knowing this would completely turn off his computer. He is now unable to boot into Windows and instead gets this screen (after a choose your keyboard screen): https://imgur.com/foEpLXE

 

None of the options we tried have ended in a successful Windows boot. When we tried to use system restore or recovery it states that there are 2 different windows installs to select from there are no recovery images no matter which you choose. It is also unable to go back to the previous version of windows. When you look at the command prompt it says X:\windows\system32 but his main drive was labeled C:

 

Startup repair also gives an error and says it saved a log file to c:\windows/system32\logfiles\srt\srttrail.txt

 

What shall we do? 

 



BC AdBot (Login to Remove)

 


#2 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,071 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:11:49 AM

Posted 17 February 2018 - 03:53 PM

See if you can get into safe mode, if so let fully load then shut it down.  Sometimes that will clear that issue.


Honesty & Integrity Above All!


#3 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 03:55 PM

See if you can get into safe mode, if so let fully load then shut it down.  Sometimes that will clear that issue.

Whoops, forgot to mention that I was unable to get into safe mode. It was one of the first things I tried.

 

Thanks so much for your help though.



#4 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,071 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:11:49 AM

Posted 17 February 2018 - 03:59 PM

Don't know if this will help but pull the battery then hold the button for about 15-20 seconds.


Honesty & Integrity Above All!


#5 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 04:03 PM

Don't know if this will help but pull the battery then hold the button for about 15-20 seconds.

This made no difference. Still got the dang blue screen with recovery options that don't work.



#6 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,071 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:11:49 AM

Posted 17 February 2018 - 04:08 PM

Did you try the roll back?


Honesty & Integrity Above All!


#7 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 04:10 PM

Did you try the roll back?

I did and also the troubleshoot startup problems. Did not work. I've pulled the hard drive to and am working on posting the log file it said it created.



#8 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,071 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:11:49 AM

Posted 17 February 2018 - 04:12 PM

Will look in later.


Honesty & Integrity Above All!


#9 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 04:14 PM

srtlog file:

 

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎1/‎28/‎2018 9:16:58 PM (GMT)
Number of repair attempts: 4
 
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 188 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 562 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 3360 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 156 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
 
Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 9453 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
 
Root cause found: 
---------------------------
Boot status indicates that the OS booted successfully.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 188 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 375 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 32 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 3375 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 156 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms
 
Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 9907 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Root cause found: 
---------------------------
Boot status indicates that the OS booted successfully.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 187 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 391 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 3688 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 157 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x0
Time taken = 18109 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Root cause found: 
---------------------------
Boot status indicates that the OS booted successfully.
 
---------------------------
---------------------------


#10 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 17 February 2018 - 04:54 PM

While I have the hard drive out are there any other log files that could be useful?



#11 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,071 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:11:49 AM

Posted 17 February 2018 - 07:10 PM

These may be irreverent but might as well run them.

 

sfc /scannow

chkdsk /r


Honesty & Integrity Above All!


#12 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 19 February 2018 - 02:56 PM

These may be irreverent but might as well run them.

 

sfc /scannow

chkdsk /r

Still working on the sfc scan. We decided to move his documents folder to an external hdd while we had it removed.

Doing a wipe on his hdd and reinstalling windows fresh is a last resort, but is looking more likely if no one else knows what we can try to do to get a successful windows boot. Thanks again for your help.

 

chkdsk:

 

C:\WINDOWS\system32>chkdsk f: /r
The type of the file system is NTFS.
Volume label is TI1068510PA.
 
Stage 1: Examining basic file system structure ...
  759808 file records processed.
File verification completed.
  27411 large file records processed.
  0 bad file records processed.
 
Stage 2: Examining file name linkage ...
  64439 reparse records processed.
A disk read error occurredc000000e
Correcting error in index $I30 for file 89A6.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 89A6.
Sorting index $I30 in file 89A6.


#13 JohnC_21

JohnC_21

  • Members
  • 23,255 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:49 AM

Posted 19 February 2018 - 03:12 PM

With the drive attached to the other computer browse to Windows\System32\config\Regback. In the Regback folder are 5 registry hives.

 

SAM

Security

Default

Software

System

 

Look at the date and size of the hives. If the date is before the problem then do the following.

 

Browse to the Windows\System32\config folder

Rename each of the above 5 hives with a .bak extension. Browse to the Regback folder and copy the 5 hives from Regback to the config folder where you renamed the 5 hives. Reinstall the drive to the original computer and attempt booting. If it fails you will need to reinstall Windows.


Edited by JohnC_21, 19 February 2018 - 03:13 PM.


#14 DavidLMO

DavidLMO

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 19 February 2018 - 03:14 PM

Did you get sfc /scannow results?



#15 kateh

kateh
  • Topic Starter

  • Members
  • 27 posts
  • OFFLINE
  •  
  • Local time:10:49 AM

Posted 19 February 2018 - 03:24 PM

With the drive attached to the other computer browse to Windows\System32\config\Regback. In the Regback folder are 5 registry hives.

 

SAM

Security

Default

Software

System

 

Look at the date and size of the hives. If the date is before the problem then do the following.

 

Browse to the Windows\System32\config folder

Rename each of the above 5 hives with a .bak extension. Browse to the Regback folder and copy the 5 hives from Regback to the config folder where you renamed the 5 hives. Reinstall the drive to the original computer and attempt booting. If it fails you will need to reinstall Windows.

 

according to the recovery log file the last successful boot was 1/‎28/‎2018 9:16:58 PM.
those 5 files in regbak are dated 1/28/2018 @ 2:48pm and are all 0KB.

 

All of the versions in the config folder are dated after the regback versions. There is still hope!

 

the sfc scan is still running.

 

Thank you so much everyone. My friend will be so excited if we can get this working. He has been without a computer since this happened in January.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users