Error booting from USB flash drive - Fossapup64 [SOLVED]
Moderator: Forum moderators
Re: Error booting from USB flash drive - Fossapup64 [SOLVED]
No need to apologize, as I somewhat thought I wouldn’t get a response at all because I finally figured out that getting a reply notification is not the default setting in this forum and looked like you marked this thread Solved about a week before I came upon it - so I figured you weren’t checking back on it. It took me about a month on this forum to finally notice there’s a check box at the bottom of a reply window, where you get the option of notifications of new posts on your thread.
Sorry to hear about the customizations not sticking, which I do find odd. I’m too new to all this to offer an answer, so can only wish you good luck with it. Part of me wonders if it has to do with it booting from the optical drive, but then find it hard to believe a mere switch out of the boot medium would be the answer. Ah well, all I can do is leave you with a hardy thanks for the confirmation Jasper.
- mikewalsh
- Moderator
- Posts: 6558
- Joined: Tue Dec 03, 2019 1:40 pm
- Location: King's Lynn, UK
- Has thanked: 1015 times
- Been thanked: 2200 times
Re: Error booting from USB flash drive - Fossapup64 [SOLVED]
@venn :-
With regard to the "hibernate" thing:-
No disrespect to Jasper, but his statement that hibernate wasn't used was irrelevant. The simple existence of the hiberfil.sys file proved that to be a false statement.
Haven't used Windoze for many years, but I still keep up with what cock-ups M$ are currently making (!!) - - and you pick up a lot of info from such articles. I came across a link to a thread on one of the Windows forums where they were discussing this very point.
As I understand it, you will never see old, "stale" hiberfil.sys files littered around your Windows partition. This file is only created when the hibernate option is selected (or automatically at shutdown, if FastBoot is active in the BIOS). At boot, the contents of this file are copied back into RAM and the hiberfil.sys file is auto-deleted.
Thus, the mere fact of hiberfil.sys existing shows that hibernation was indeed active at the time the screenshot was taken. @one was quite correct about that.....and hibernation WILL "lock" the disk, and prevent writes from being made.
Mike.