• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Slow load after logon (Windows 8) - Resolved

destrekor

Lifer
So, as a preface, this thread covers what I suspect has something to do with this. This is a new issue, and I very much suspect it is due to everything that has been done.

This system is not on a domain, this is a standard login, though it utilizes my Microsoft Live account. I have it set to use a pin.

So, after putting in my pin, it takes way longer than usual to get to the desktop. So long, that the lock-screen image actually comes back, and you wouldn't be able to tell that it is currently trying to login at that point. If I let it sit for another moment, it eventually kicks out of the lock screen and loads the desktop.

Their are no additional programs set to load on startup, in fact, I've actually been cutting startup apps and services (none essential, there is zero [0.000001%] chance what I've cut has now started delaying login).

As I type this, knowing that it is an online-connected account (though cached credentials, so it should not matter), I'm going to reinstall the Intel NIC driver and see how the system responds.
 
Last edited:
I re-installed the latest Intel NIC and Intel MEI drivers that are listed on the Asus website for my P8Z68 Deluxe.

No change. 🙁
 
Aha - I think the SES driver for my WD external drive needed reinstalled. There was an update on Windows Update for that, I installed it along with one recommended update (for camera file formats according to the KB article, probably good for RAW support), and one optional update for a Diagnostic Tracking Service. With those being the only other updates, I feel certain the SES driver either needed that update or simply needed to be reinstalled.

Consider this resolved.
 
Back
Top