Classic Shell: Forum

Hello Ivo,

I just noticed that my fast boot option just stopped working, but only if I leave my PC off for an extended period of time (eg overnight or hours) and I am not sure if Classic Shell has anything to do with it but here is what I found out so far:

Checked Event Viewer and found this log:



Next, I also noticed that Classic Shell is not working (eg Start button returns to default Windows 8.1 operation).

So, to further investigate what issues I might be having with fast startup and the above log referencing an unknown wake timer, I input the following message. Note the response:



Legacy kernel driver? So, on a hunch, I uninstall Classic Shell 4.02, reboot, and reinsert the same message again:




Now all of this is way beyond my technical understanding; however, I just wanted to give you an FYI to see if any of the above makes sense to you. Anyway, I am running a clean install of Windows 8.1, using the latest GA ISO via download trick at eightforums.com and all available Windows Updates have been applied to current. THe only other issue I have had thus far is 5 app updates that failed to install (initially) from the Windows Store; however, I went back a day later and they all updated just fine. However, I don't care anything about apps or use any of them either.

So, now the BIG TEST will come tomorrow when I attempt to power on my PC again and see if my fast startup functionality has returned to normal. I'll report back at that time. Please understand that I am just throwing this out for your consideration to see if it rings any bells for you because I can't hear any.

Thanks,

njgroundhog

UPDATE: Since uninstalling Classic Shell 4.02 I have observed the following changes:

The "returned from low power state log - waketimer unknown" log is gone and I am now receiving more informational logs (went from about 23 to 48 FYI logs), and among them were this new one which was not appearing previously:



Now, one other thing I have noticed is that the shutdown "now" takes about 3-4 seconds which seems normal to allow for data to be written to hiberfil.sys; however, when I had Classic Shell 4.02 installed, the shutdown was almost immediate and never took longer than a "blink of an eye." It almost seems like it was attempting a forced shutdown that did not allow for adequate time to write the "state" information to hiberfil.sys. Maybe this is all for naught and has nothing to do with Classic Shell but I'll know for sure tomorrow. Thanks.

Classic Shell is a suite consisting of a Start Menu, and Explorer+IE plugins. It does not affect other programs or the operation of the system. It is not a full shell replacement and does not modify Windows in any other way, nor does it install any kernel drivers or send power availability requests. It also does not affect sleep or shut down functionality. Some other program is causing this.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

OK, thanks for that explanation so there is no need to further update this thread.

Thanks you for your time.