Page 1 of 1

I can't start up win 10

Posted: 17. Apr 2019, 18:53
by deYo
Starup Repair couldn't repair your PC
Press "Advanced options" to try other options to repair your PC
Log file:E://WINDOWS/System32/Logfiles/Srt/SrtTrail.txt

All try all options but cant start
Anyody help?
BR Dejan

Re: I can't start up win 10

Posted: 17. Apr 2019, 19:04
by socratis
Did you change anything in VirtualBox to cause that message?
Why do you think that this is a problem with VirtualBox and not a problem with your guest?
Would you call Acer/Apple/Dell/HP/Lenovo/other if you had such a problem?

Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

Re: I can't start up win 10

Posted: 17. Apr 2019, 19:35
by deYo
All working ok and next day windows can't start. I have not say that is in virtualbox problem..I try find solution for solved problem and start windows without reinstall and lost data.
BR

Re: I can't start up win 10

Posted: 17. Apr 2019, 19:48
by socratis
Can you post the file "E://WINDOWS/System32/Logfiles/Srt/SrtTrail.txt"? ZIP IT first.Or you can't even access the files?

Also, search for "SrtTrail.txt", there are a lot of similar issues out there!
deYo wrote:I try find solution for solved problem and start windows without reinstall and lost data.
You could install a 2nd Win10 VM and add the VDI of the first VM to the new one and retrieve your data.

Re: I can't start up win 10

Posted: 17. Apr 2019, 20:41
by deYo
I try in DOS search this file and this file not exist.

Re: I can't start up win 10

Posted: 17. Apr 2019, 21:13
by socratis
Follow the instructions here: https://ugetfix.com/ask/how-to-fix-srtt ... indows-10/ and simply ignore all the "FIX IT NOW" links, do not download anything. Just follow the text... Or as I said search for "SrtTrail.txt".

As I said, this is not a pure VirtualBox problem, treat it as a Windows problem.