Screen Goes Black After Login in Windows 7 Updated FREE

Screen Goes Black After Login in Windows 7

• Remove From My Forums

windows 7 black screen subsequently login, no desktop prove upwardly

• Question

• Hi everybody, I'thousand having trouble with my windows seven right now, information technology'due south an ultimate version, I simply shut it off last night and opened it up this morning. Everything seems to exist normal util I loged in to my user. The old things happend after that, just the black screen showed up and an window popular up which shows "my reckoner" the mouse can be moved regularly.
  I tried several ways to get information technology back to normal:
  reboot.
  reboot and login to safe mode.
  alter the resolution and multiple monitor settings.
  uninstall and reinstall the graphic commuter.
  ctrl+alt+del will allow me go to the regular screen which I could get to the task manager, switch user, lock the pc, signoff, change laissez passer word, and reboot or restart etc.
  I concluded the "dwm.exe" in process which would not work.

  That window seems like the simply promise I could admission the computer which pop upwards everytime I reboot.

  I tin utilise that pop up window to become online and go control panel and all that, I tin also run all the programme just like normal. Everythings sames normal also I cannot get the normal screen, no starup, no destop icons, no quick lunch. I could change my background film, but I cannot use right click on the background.

  Does everyone know how to solve this? I really don't desire to reinstall the windows again which I only did a calendar week ago.
  I will appreciate whatsoever solution to this problem.

Answers

• I fixed this issue, I as well had the aforementioned problem. Here is how I did it.

  1) Reboot and press F8
  2) Select "Repair my figurer"
  3) Select the keyboard layout and lanugage
  4) When you reach system recovery tools, select Organization restore.
  5) Select the restore indicate when it was working fine and restart the computer.

  That's information technology....

  If you do not have the system restore points, try startup repair.

  • Proposed as reply by Sunday, January 31, 2010 3:11 PM
  • Marked as answer past Anthony_Mann Monday, February 1, 2010 one:55 AM

• This isn't an authoritative answer - I've but had this problem, sifted through the initial artificial media coverage, constitute a solution, and started speculating on the existent cause.

  Here's a workaround for the problem, though this visitor mis-diagnosed the problem (it wasn't an ACL problem).  This ready is opaque and comes from a third party, merely it stock-still the problem for me:
  http://world wide web.prevx.com/weblog/140/Black-Screen-woes-could-affect-millions-on-Windows--Vista-and-XP.html
  Annotation their fix is an exe and they don't tell yous what information technology does.  I appreciate that they are helping, but they should fully disclose their fix so at least avant-garde users can have confidence in their good intentions.

  Here's a better possible reason for why the problem occurred (a registry key telling Windows which shell to run on login was corrupted - a REG_SZ key was missing a '\0'.  Sounds somewhat plausible, simply the fishy part is what caused that?):
  http://www.prevx.com/blog/141/Windows-Blackness-Screen-Root-Cause.html

  My symptoms & observations:
  I ran into this trouble on a Win7 laptop that was upgraded from Windows Vista Ultimate.  I log in, become a black screen, and Windows never gain to setting up my desktop, etc (ie, Windows never launches explorer).  Running the fixing tool from Prevx did solve the problem, however their diagnosis for the cause of the problem was wrong (their initial hypothesis was the ACL's were incorrect and implied Windows Update patches broke it, simply that was wrong.  They followed up with the non-null-terminated cord hypothesis).  Before running Prevx's tool, the registry key existed, RegEdit visually displayed the expected value (explorer.exe), and the ACL's were fine.  Still, of class, I couldn't successfully log in.

  My pure speculation about the cause:
  So if the missing '\0' hypothesis is right, and if the Prevx tool deletes & recreates the value in the registry key, obviously that should gear up the trouble.  (FYI - look at the MSDN docs for RegSetValueEx for a note about the lpData parameter needing a '\0'.)  Only that doesn't explain how the value got messed upward in the starting time place - I don't go around removing terminating zeros from REG_SZ values for fun nor profit.  Sounds like either random corruption, or more than likely, something wanted to run something when Windows boots then incorrectly undid their change to the registry.

  I saw that some MS security folks suggested this could be caused by malware (http://blogs.technet.com/msrc/archive/2009/12/01/reports-of-issues-with-nov-security-updates.aspx).  Operating under that hypothesis, I ran Forefront on Wed using the current signatures, but it didn't report anything.  That may non spot a novel virus or rootkit, of course.

  Some other wild judge - perhaps the act of installing certain classes of patches could cause the problem, due to a (hypothetical) bug in Windows Update.  Windows Update does something on kick up to configure patches, and it looks like this happens afterwards login merely before Explorer is running.  Perhaps Windows Update itself could exist editing this registry key to replace the crush with some other program that configures patches (or options to explorer.exe?), and then replaces the registry primal again to betoken dorsum to explorer afterwards patches have been installed?  If that's how information technology works (which is a big estimate), then maybe when WU restores the registry key value to explorer.exe, information technology doesn't reset this reg key accordingly on Win7.  Of class, I would have expect to see a bad value for this reg cardinal in RegEdit if this were the case.  I didn't - perhaps in that location were some unprintable characters in the string, or I've empirically shot downwards my own wild estimate.

  Note - my problem occurred on a Windows seven Ultimate machine that was upgraded from Vista Ultimate.  Perhaps something during upgrade may have introduced some registry corruption that didn't show up until another value in the registry was changed after?

  BTW, to confirm the fix & narrow down this set, perhaps someone w/ a broken motorcar can reboot into Safe Mode, run RegEdit, delete HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell then recreate the Vanquish key as a REG_SZ primal, with the value explorer.exe.  If that works, that could assist confirm the cause and let us to give standalone instructions for a fix that we can accept more conviction in (every bit opposed to telling people to run an exe from a third party).

  • Proposed as answer by Blair Briggs Fri, Dec 4, 2009 6:40 PM
  • Marked as reply by Anthony_Mann Monday, February ane, 2010 one:57 AM

• I had the same trouble, until a few minutes ago. My trouble was that I had a NAS box prepare on my local network, and three drives mounted and mapped the the Windows machine. I was getting ready to reinstall, when I tried rebooting the machine without networking in safemode.

  The NAS was responding to a certain bespeak, don't know which, didn't care, rebooted it (It was a QNAP Turbo NAS 219P) Then tried again, now that Windows didn't try to map the drive, explorer worked once more!

  Problem: Windows explorer was trying to mount these and map them, but timed out a dozen times or so, catastrophe in a malfunctioning explorer.

  Test: Pull out ethernet, or turn off router before login, see if it helps, if it does, apply fix. If it doesn't, this was non the result and I cannot aid.

  Fix: Restart whatever machine you've got mapped to your motorcar, or turn it off, it'due south gotta need some repair.

  • Marked as answer by Anthony_Mann Mon, February 1, 2010 1:56 AM

• I experienced this trouble today afterward installing an awarding called "Neatscan to Office one.0". The program appeared to install correctly and documents could exist scanned into Office 2007 programs.

  Upon reboot I encountered the "Black Screen" forth with the message "The procedure entry point DwmHintDxUpdate could not be located in the dynamic link library USER32.dll." Attempting to manually beginning explorer.exe was unsuccessful.

  System restore to a point a couple of hours before the install, fortunately, corrected the problem.

  Scout what you are installing. Neatscan claims Vista compatibility, just does not appear to want to play prissy with Win7.

  System Info: Dell Latitude E6400, Windows vii Ultimate 32-bit.

  • Marked as answer by Anthony_Mann Monday, February 1, 2010 i:56 AM

• I'm on Windows 7 Ultimate, a brand new install (not an upgrade).

  There was a lot of "printing" online, even from reputable technical sources, around this by Thanksgiving nigh prevx's claim and that it was a hoax and maybe even unsafe.  I held off for a couple of weeks, hoping to see Microsoft come up out with some sort of argument acknowledging that our experiences were real and at to the lowest degree begin working on a solution.  I never saw one.

  I somewhen decided to repeat what Brian had discovered and washed, running the prevx.com fix (http://www.prevx.com/weblog/140/Black-Screen-woes-could-affect-millions-on-Windows--Vista-and-XP.html).  I haven't had the problem since and information technology'south been almost 2 months.  Based on this, I recommend others try it too.

  My thanks to Brian's experiment and recommendation.  With Brian'south link from Microsoft posted here, I had reasonable conviction I wouldn't mess my system up.

  Jon

  • Marked equally answer by Anthony_Mann Monday, February 1, 2010 i:56 AM

Screen Goes Black After Login in Windows 7

DOWNLOAD HERE

Source: https://social.technet.microsoft.com/Forums/windows/en-US/5b94b775-992e-4f48-b3ff-c89b3cf45e82/windows-7-black-screen-after-login-no-desktop-show-up?forum=w7itprogeneral

Posted by: kevinwharleas98.blogspot.com