KB3097877 causing severe difficulties for some Windows 7 users November 2015 Windows updates — 111 Comments

  1. Seeing flashing screen just after seeing login prompt on Dell Latitude 7450 with KB3097877, unable to login locally, remoted into machine adn uninstalled patch adn then was able to login normally.

  2. After installing this, the monitor turns off like the GPU is resetting itself, then I get a black screen with a white cursor. Can’t do anything except insert the Windows 7 install CD and run a system restore.

  3. I have this issue, login background screen loads and starts flashing but no option to login, tried starting in safe mode and safe mode with cmd prompt but just loads the above and that’s it.

    • darren – if you haven’t cracked it yet – select the “first” option “repair your computer” (the one already highlighted).
      I tried safe mode with networking etc and non of them worked. The first one got me to sys restore and it worked a treat.

  4. If you cannot login, I just fixed a sale’s guy machine by restarting machine, smash F8 until you get the advanced boot options screen, go to Windows Restore and restore to yesterday’s date. Once finished, go in and turn off automatic updating (or at least tell it to require your permission to install updates). In the meantime, wait for Microsoft to pull the rouge update.

  5. Potentially found a fix for this issue.

    You’ll need a recovery cd/usb

    In the recovery console get to a command prompt
    from there type:

    dism /image:d:\ /remove-package /packagename:Package_for_KB3097877~31bf3856ad364e35~amd64~~ /scratchdir:d:\temp

    The ” ~amd64~~ ” is for a 64bit system
    I would assume you’d replace that with ” x86 ” for a 32bit copy of windows

    • I am trying to use this command line to remove the update, but it is not working. I have an HP and the image is on D, but I can determine if this command line has any spaces that I am not typing in such as: is there a space between /scratchdire:d:\temp??

      i am getting Error: 1639 “The command-line is missing a required servicing command.

    • Same solution we came up with. Boot to recovery console command prompt or Windows Preinstall Environment USB key and run:

      dism /image:c:\ /remove-package /PackageName:Package_for_KB3097877~31bf3856ad364e35~amd64~~

      where c:\ is the drive letter of your OS partition

  6. Pingback:#KB3097877: #Outlook crashes with error C0000374 (FIX) and other issues | Born's Tech and Windows World

  7. I have the same problem with windows 64 bit.

    i have managed to get to a command prompt but i dont have the skills to develop the message to type in can anyone help with the correct command message please

  8. Thanks Selby … saved me a bunch of time, though I typed one of the ~ in as a hyphen so still had to use /get-packages and wade through to find the right one, only to see it was exactly as you typed 🙂 I’m back into Windows now anyway.

    Curly – that dism line Selby showed above worked for me but you need to work out in the recovery cmd prompt which drive your Windows installation is on, and then that becomes the drive letter referenced in the /image and /scratchdir options (above Selby used d: but for me it was f:)

    Good Luck!

  9. If you can’t login and have two monitors, try unplugging the other one.

    Also, what I did was to login to my PC from another PC via remote desktop; worked just fine. I removed the offending update, rebooted and all was well.

    Poorly done by MS, I have to say.

      • Okay some movement – perhaps someone can help with thi bit?

        After some confusion typing in the command line, turns out I was using the wrong tilde (DOH!) It found the file in the DISM, but gave me an error 87 – saying that image is trying to run on a running Windows file, and I should try /online or /online /?

        I do not know what this means, does anyone else?

    • Selby said he was successful using an image on a dvd. I tried this and IT WORKED! Thank you selby. By the way I made X = D and /scratchdir:C:/temp Note that I used the C: drive for the scratchdir because evidently it needs to be quite large.

  10. I tried entering the line into cmd prompt and have changed out the X to C etc. I’ve done this a couple of times, each time goign through letter by letter to check for errors. I believe I have copied it perfectly.
    An error is coming up saying:
    Error: 267

    An error occurrred while accessing the temporary directory.
    Ensure that the path to the directory exists and that you have Read/Write permissions on the folder. For more information, refer to the help by running DISM.exe /ScratchDir /?

    Question: My computer shows “X:\windows\system32>C:”
    Is it possible that in the line given I need to change ~amd64~~ to ~amd32~~ or alternatively amdx86?

    I feel like it’s an issue of location and I know that my windows stuff is all saved to C: drive so I feel like it’s further down the line that the issue occurs.

    • I had to create the temp directory. “d:\MKDIR temp” in the D: drive. I have an HP and the system directory is C but my installation of Windows is in D:. Worked awesomely. Thank you!

    • for me it was finding the right drive path

      typing in cmd: wmic logicaldisk where drivetype=3 get deviceid, volumename, description

      will show which drives are your local drives, try each letter, also make sure that the temp folder exists, you can do this by typing “mkdir temp” after you navigated to each drive

  11. There is no need to run this through a recovery mode. You can very well run the command under a normal windows session mode and after few seconds the computer will reboot without warning. This fixed my sidebar issue straight away.

    • If you can log in to the computer then you can uninstall the offending update by using control panel => programs and features => view installed updates and then right click the kb:3097877 update and select uninstall
      you only need to go through the DISM process when you cannot log on to windows ( this is happening to fewer users than the sidebar or outlook issues, but is more difficult to fix)

  12. I also experienced the flashing screen in combination with the log-on prompt (I own a 5 year old Dell that runs Windows 7). I managed to log-on by selecting ‘Safe mode with networking’; for some reason ‘Safe mode’ did not work.

  13. I work in an it department in the education sector. We found the best way to fix this is a system restore.then just hide the update. if you can log in then uninstall it from the control panel

  14. Yeah i had an issue with using the method stated above but i just used this without the scratchdir:

    dism /image:d:\ /remove-package /packagename:Package_for_KB3097877~31bf3856ad364e35~amd64~~

    My windows was installed in the “d” directory. All is good now. Officially disabled all windows updates after this stuff up from Microsoft, Half thinking about going converting to OSX…….

  15. Thanks Selby, managed to connect to C$ from working pc and create fix.bat and copied your command into it. Then ran repair on didgy PC and from command prompt went to the directory and ran it. Worked perfectly.
    It is strange that at the moment it has only occurred on one of my PC’s I have about 25 of the Dell optiplex 780’s with windows 7

    • The Microsoft KB article says that they have issued a revised patch that fixes the outlook issue but there is no mention of the log in failures. Microsoft have so far not acknowledged that as a problem

  16. Pingback:Blank screen after pressing CTRLALTDEL for login. No way of logging in across Domain. - Page 5

    • Uninstall it and try the updated patch & see if that solves the Excel crashes. I have seen a few comments saying that Word crashes with this update when it uses images, graphs or complicated/nested tables as well

    V2.0 (November 11, 2015): Bulletin revised to inform customers running Windows 7 that the 3097877 update has been re-released to address an issue that caused crashes for some customers when they viewed certain emails. Customers who previously installed update 3097877 should -reinstall- the update to correct this known issue. See Microsoft Knowledge Base Article 3097877* for more information.

    Last Review: 11/11/2015 22:26:00 – Rev: 2.0 – “… Issues in this security update: We are aware of reports of crashes in all supported versions of Microsoft Outlook that occur when users are reading certain emails after this update is installed…”

    • Just look at the comments here Jack, That revised update might have fixed the outlook crashing bug in this patch, but does NOT seem to have cured other bugs involving logging on or PPT or Word/excel
      Microsoft have still not acknowledged that there is a log on problem.

      Several other sites seem to think that it only involves touch screen devices ( even where touch screen isn’t actually enabled, or where an on screen keyboard is enabled by default )
      I am open to suggestions about that, but there does still seem to be a problem that isn’t being fixed by the revised update

  18. KB3097877 automatically downloaded overnight. Computer, which had been on standby, worked fine until I rebooted and was faced with a flashing screen. Used F8 and after trying several options eventually recovered the system by way of a 2 day old restore point. All personal files, Word, Excel, internet OK, don’t use Outlook. I have now set Windows Updates to check and let me know! Thanks to all helpful comments above.

  19. “… does NOT seem to have cured other bugs involving logging on or PPT or Word/excel
    Microsoft have still not acknowledged that there is a log on problem.
    Several other sites seem to think that it only involves touch screen devices ( even where touch screen isn’t actually enabled, or where an on screen keyboard is enabled by default )
    I am open to suggestions about that…”

    This M$ QC problem has been ongoing for 2 -years- now – ‘only suggestion that works for me is ‘wait ’til near month-end, when the patches have had more ‘end-user testing’…

  20. I can’t get to the restore screen. I’ve tried all options for Starting normally, in safe mode, etc and pressing F8 isn’t getting me anything. Still a flashing screen with Windows7 Home Premium at the bottom.

  21. Ref:
    Last Updated: 2015-11-12
    [Comments] “… The issue with Outlook is apparently fixed but the -other- Windows issue not according to multiple sources. RE:
    2) Microsoft has -not- addressed the reported issue of blank or blinking screens after attempted logins that was supposedly resolved by removing this patch, according to some users. A few users are reporting this happens on touch screen systems with on-screen keyboards only and remote controlling them gives them access when the issue happens; some are also saying this happens of regular PCs but remote controlling also works. All are saying uninstalling the patch fixes the problem.
    ‘… These are hardened systems where even us (IT) do not remote in because we can simply go to the system if something needs to be done at it physically. Are we basically SOL? We can’t be the only ones in this boat. The only way I can think of is a 3rd party tool to boot the system and allow edits to the registry (dangerous at best). This is really bad.’ ”

  22. Was getting an error upon reboot that explorer.exe could not start 0xc0000022
    If you can get to the task manager, you may not have to reinstall/repair anything:

    In task manager:
    Applicaitons tab>New task>powershell.exe
    In powershell type in: Start-process cmd –Verb RunAs
    Accept the UAC prompt
    In the new window run: explorer.exe
    From there you can go to control panel, uninstall the windows update

    Alternatively, you can run the uninstall command from the prompt as well like BDUB mentioned

    wusa /uninstall /KB:KB3097877 /quiet /norestart

  23. When I use the dism script I am getting the error message Error:1639 The command line is missing a required servicing command. Any ideas what I am doing wrong?

  24. For information only: my computer (using Windows7 Home Premium, v6.1) is touch screen which may be to relevant to this issue and before I solved the problem I was using an on-screen keyboard. To open the System Recovery Options menu at start up I used a USB keyboard and pressed F8 repeatedly.

  25. I am a one to one school in Louisiana. I have taken in over 50 computers since yesterday with this issue. I am replacing HDD with a fresh copy of untainted Windows. Cant seem to get the command prompt to come up, so replacement was my only option. I really would like to hear how MS will explain this fiasco! This is DIGUSTING!

  26. I’m trying to do a system restore back to 11/09/15 but it’s stuck on restoring files… tried several times and it just gets stuck for hours on restoring files

  27. ********************************************************************
    Title: Microsoft Security Bulletin Releases
    Issued: November 12, 2015


    The following bulletins have undergone a major revision increment.

    * MS15-115 – Critical

    Bulletin Information:

    MS15-115 – Critical

    – Title: Security Update for Microsoft Windows to Address Remote
    Code Execution (3105864)
    – Reason for Revision: V2.0 (November 12, 2015): Bulletin revised
    to inform customers that the 3097877 update for Windows 7 and
    Windows Server 2008 R2 has been rereleased to correct a problem
    with the original update that could cause some applications to
    quit unexpectedly. Customers who have already successfully
    installed the update on Windows 7 or Windows Server 2008 R2
    systems should reinstall the update.
    – Originally posted: November 10, 2015
    – Updated: November 12, 2015
    – Bulletin Severity Rating: Critical
    – Version: 2.0

  28. I wouldn’t do that. Just use RDP to connect to the computer and check for updates and install the new patch for KB3097877. If that doesnt work then uninstall the previous version of that update and reinstall the new version or just hide it. Will save you a ton of time than replacing hard drives or any other route.

  29. I have Win 7 Professional on a Panasonic CF-C1 Tough book (touchscreen) with the login loop problem. I’ve tried to do a System Restore to several previous points and I get an error 0x8000ffff during the restore.

    Any ideas? This is seriously retarding my day.

    • Update… the System Restore said it couldn’t be completed. I just clicked through OK and clicked restart system in the dialog box.

      System Restore was actually successful and I’m logged in and running again.

      VERY tempted to click the Windows 10 upgrade box now! It’s a conspiracy!

      Thanks for the help from these comments!

  30. Okay, I appear to be one of the unlucky ones.

    I have an ASUS Z8500 (or close) with a touch screen, about 5 years old, never had a squeak of a problem (bar slowness) with the OS. Installed this update this morning, been without my main computer ever since.

    I believe I have tried everything I have seen in the thread, although for the line items, I am not sure the syntax is right for my machine (Windows lives on the D drive). I tried to roll back the update, and it didn’t work, and deleted the restore point. I am not sure about remote access – I have something called network magic, not sure I can use it for this – I haven’t used remote access before. There appears to be some kind of patch on the MS site, but it seems to need downloading to the machine that I cannot log into.

    This comes on top of a Windows 8 fiasco where the restore disk didn’t work (the power went off during an update) and PC World will not give me the access code, and Microsoft insists that the manufacturers have it. They each want me to buy another copy of Windows 8, so there you have it – yet another dead computer, though granted that i the paranoia that MS has to prevent having a backup disk provided – with a code – when you buy the software. But I digress…

    I feel like I have tried everything, but if anyone knows of a way to access the machine remotely without prior set up I would be most grateful – the only obvious fix is to take this hateful software off the flippin’ machine. However, any and all advice gratefully accepted.

  31. Hi,
    thanks very much using the code in repair console i was able to make pc login again…


  32. Hi all, so it looks like we’re all being affected by this update.

    I’m running Windows 7 on a hand-me-down ASUS notebook, that doesn’t have a disc drive.
    Same story, booting up past “starting windows” screen and once it reaches what would be the login prompt, my screen flickers and the cursor/loading wheel flash along with it.

    After checking out the windows site and punching in my product key to DL a copy of Windows 7 recovery ISO, I’m prompted with a screen saying that my computer was pre-installed with Windows, and in order to continue, suggesting that I contact the manufacturer, ASUS.

    ASUS doesn’t have any DL’s on their site for a matter so specific to this change. Anyone else out there with an ASUS machine have this issue/solve it?

    NOT to add insult to injury but my keyboard is also a bit wacky, in that nearly 10 letter keys are inactive (after years of use).

    I know its a long shot, but any feedback would be appreciated.


    • I also have an OEM version of the software – I called MS this morning, and where I didn’t take this option for other reasons, it is worth pointing out that they caused the problem, they should fix it – they can offer you a code that will work for the download. I also got a case number, but that took two days – find out which region you are in, and you can call the help desk for Volume Licensing.

      They didn’t have the expertise (yet) to solve the problem, but that is an option I will try and request specifically. I’ll keep you posted.

  33. Someone mentioned a patch. I was thinking the same thing. Why doesn’t MS just make available something we can download and burn to a CD and just plop it in and it fixes the problem? I’ve spent ?@#$@$!@ hours trying to get this fixed today and still no luck. When I try the command line stuff it says it can’t find that package, and I quadruple checked the spelling/characters for typos etc. Anyone know if MS has anything available to easily fix this? I’m shocked if they don’t. How can they expect normal users to have to go through all of this technical crap? There have to be at least a million people completely locked out of their PCs right now with no way to fix the problem…

    • My question, since I can’t seem to make any of the command line fixes work. IF the new UPDATE does indeed fix the problems. And I’m not sure it does. If you can’t log on to your computer how are you supposed to download and apply the update?

  34. Two separate, non networked, Sony/Microsoft computers displayed blinking blue screen on startup. I recovered the home pc with a recover one day before the November patch. The professional pc is in Microsoft repair center in critical condition. Microsoft is trying to blame us, go figure. I hope it can be restored. I can’t believe Microsoft pushes updates with corrupted files???

  35. Have tried everything. The command line stuff says the package can’t be found. I’m totally locked out. Seems like MS should have created a downloadable fix by now that you can just burn to a CD, plop it into your fubared PC and get it fixed. Anyone know if such a thing exists yet, from MS or anyone else?

    • I had the same problem. Don’t assume you have everything set up on your C drive. I made this mistake. Then noticed that when I tried system restore (which didn’t work) the box said Windows 7 was on D drive. If you replace the C with your correct drive then all the updates will appear . dism /image:D:\ /get-packages
      Be warned they whizz past so keep stopping the list, press enter to move on, until you get to the security update packages. If you let the list complete before finding the correct update, you won’t be able to find it for some reason as you can only scroll up so far. That’s what I found anyway.
      The code they give has x86, but mine was amd64, so make sure you copy down the full code properly and don’t just use the one the website gives.
      It has worked for me, but with some trial and error. Good luck

  36. Black screen on boot problem; boot to command prompt from hard drive also locked up but worked from USB install drive. The DISM command refused the /packagename param but accepted as ..

    dism /image:X:\ /remove-package:Package_for_KB3097877~31bf3856ad364e35~amd64~~ /scratchdir:X:\temp

    Dism could not locate the above package?

    • make sure the X is the same as the drive that windows is installed on
      it might be C: or D: or E: or F:
      it all depends on whether you have used a USB /dvd drive to boot to recovery options or whether you have managed to use the inbuilt recovery options

      Microsoft have now updated the Information on the KB with full instructions including pictures showing how to do it

  37. This is for those who can boot to a Windows 7 disk. If you were like me and can’t boot to safe mode, command prompt, or see System Recovery Options when booting, just boot to disk and choose your language. Press Shift+F10 and you’ll see a command prompt window. I then proceeded to type in the dism line from this site to uninstall KB3097877. This successfully allowed me to log into my Dell XPS 27 AIO computer again! Thanks Derek for your post.

  38. Same problem here with an Asus EEETop 23″ with touch screen, no login screen for any users account.
    After that I knew of the problem of KB3097877, from bios I disabled the touch screen, so now I entered in the user account, and then I uninstalled the malefic update.

    Thanks for your support 😉

  39. Okay, some movement, I don;t know if anyone else is at this point.

    I have spent no kidding 2 hours 40 minute on the phone with Microsoft. The phone was just disconnected – how happy I am.

    After working out that I was using the wrong tilde (doh!) I was able to use the dism string above in the command prompt.

    I then got the message saying that image/ was trying to work on a running Windows installation, and wanted me to use online / or /online /?

    Does anyone know what this means?

  40. Pingback:Anonymous

  41. This is so crazy. After messing with this for at least 8-10 hours over the past few days, now DISM doesn’t even seem to work. If I just do “dism /image:D:\ /get-packages” it says that the get-packages option is unknown. WTF??

  42. Wasted most of yesterday 12th trying to fix this. Even used a linux utility for Windows password removal. I just kept getting the loop back to the login icons screen, whatever I attempted. Unfortunately the day before I’d run Ashampoo WinOptimizer which had removed any possibility of roll-back/recovery. Booting from a Win7 DVD didn’t help either, I could get to a command prompt but my C: Drive was then a D: drive, which made resolving the problem even more difficult. Switched the PC off and gave up. This morning had several attempts, no joy but then, on rebooting, another update came through… I kept my fingers crossed while it installed and hey-presto I can log in again.

    So the technical solution is:
    1.Switch off the PC.
    2.Go to bed and DON’T THINK ABOUT THE PROBLEM!
    3.Keep fingers crossed.
    4.Don’t get up too early and have at least one cup of coffee before powering up your PC.
    5.Keep fingers crossed and switch it on … and (as usual with Windows) … wait a while…

  43. Thank you all so much for this thread. I was ready to shell out bucks for a new computer before I found this.

    I had been trying to restart and use the F8 key to get into the command prompt like you all had described– Windows was booting up and I thought I had missed the “window” in which to press the key- so out of frustration I just shut it off and turned it back on. When I turned it on again I got a message telling me that a previous start-up had failed, and would I like to restore my computer to a previously saved restore point? Why yes I would. It restarted itself after that, and then on the second restart it asked me the same thing. I said yes again, and it took a LONG time- I actually left the house, and when I came back, I came back to a computer that would let me log in without the flashing screen. It’s been fine since. I don’t know if I would advocate turning your computer off and on while it’s booting up, but I think I got lucky! I went into automatic updates and unchecked this particular update so that hopefully this won’t happen again.

  44. Thanks so much, I followed the pics on the Microsoft link and computer is up and running.
    Three times I contacted Microsoft support. All they said was to re-install windows. Even after I explained about removing KB3097877.

  45. What are people supposed to do when none of the above works? Reinstall Windows and lose everything? Yeah right. I don’t understand why Microsoft doesn’t just make available a downloadable image that you can burn to a CD, plop it in your screwed up computer, and it just automatically fixes this problem? I will go buy a Mac before I re-install Windows AGAIN. Can anyone help or am I just screwed? I’ve tried everything mentioned in this and all other threads. It keeps saying that package isn’t available. Anyone??

  46. Thanks a lot. It worked for me only after using dism /GetFeatures command, copy and paste exactly KB3097877’s package name. Thus dism command with “/Remove-Package /PackageName” option worked well

  47. I have a Lenovo A700 Idea Centre.
    Not working all week. Can’t log in. Can’t use safe mode. Only way to restore is F2 but all data will be lost. Nightmare.

  48. Got flashing screen and unable to do anything – took to Currys who said I was the third person with this problem to go to them – only option to restore to factory settings – asked about saving data on hard drive – told this might be possible but cost me a total of £169 and a wait of 10-14 days to see if it could be done – had to but an external hard drive for the recovered data – are Windows offering compensation for what they have done?

  49. Pingback:Outlook 2010 en 2013 crashen - Van Rosmalen Automatiseringsdiensten

  50. Okay, after quite a lot of hassle and time, I think I have cracked it – it is the small things left out by technicians that can sometimes make all the difference to the outcome.

    I stood back from this for a few days, but here is what the article on MS website did not say.

    You will need to copy and paste in the command prompt for this to work – typing it out (in my case) was not working, and hasn’t to date, even though I had it exactly as it was listed. I have gotten beyond the blink for the first time! So, if you do what MS says and

    dism /image:C:\ /get-packages :more

    IMPORTANT:THIS SHOULD BE A VERTICAL LINE, NOT A COLON. I don;t have a keypad for this, but if you hold down the ATL key, and using the keypad, type 124, you will get a vertical line (It may look like a colon made with two lines – this is okay)

    The reason you want this, and “more” is so that, using the spacebar, you can go to the actual entry in the packages. It seems that this is the only way to get it to work on fussy machines. If you let it scroll to the bottom, it may “cache” out, and you cannot scroll back up to it.

    ONCE YOU SEE THE ENTRY, you can use the cursor to highlight just the Package name:

    N.B. you need to use the little box at the top of the screen on the left side. It has to have “QuickEdit Mode checked”. Then, you highlight, and copy. Then, (assuming you have the right drive) you type in the rest of the line just as shown: dism /image:C:\ /remove-package /PackageName:

    For me, clicking there pasted the text. It worked immediately.

    It took a couple of minutes, and gave me a warning first about the memory, but in my case at least there was no issue.

    There is so much helpful stuff here, thanks to all contributors, but this may help resolve the issue for others – it is probably obvious to some, but not to all. Good luck – I am all the way back in, and over the moon 🙂 Thanks again to Derek for putting up the post.

  51. The problem for me is that it has changed the C drive and called it E. I have followed the instructions and successfully removed KB3097877 – there were two versions – and but restarting still leaves my computer hanging

    • Well, that part was confusing for me as well. The prompt was on X:, but the actual Windows installation was on D:. If I did it on X:, it said that Windows was running – which confused me because it wouldn’t – but actually, it does say Windows at the prompt. I had tried on D:, but that was when I was typing it in. When I did the wierd copy paste, lo and behold, a working machine (and I got the same BS about reformatting the drive…)

      Further up this thread it says how to identify where your Windows installation is. This is a pfaff to be sure, and I can’t tell you how annoyed I am that after 2.5 hours on the phone with MS, they turned out to be as useful as a chocolate fireguard. Anyway, when you know where windows lives, put that in the image instructions. It won’t work if it is the wrong drive anyway, but that, and the above, in theory, should allow you to delete. It was days before all of the “right” stuff worked. All I can say is good luck 🙂

      • Yes indeed it does take reading the instructions more than ONCE to get the idea. Since most people are used to windows being the “C” drive I’m sure many frustrated people were to surprised to find out that in RC mode the drive is usually “D”. And so it went with the first posting.

        BUT as more people had problems with understanding the instructions got more clear and more clear, the syntex got got more clear and more clear. Till finally it was quite easy to do the fix correctly.

        And I for one, applaud and THANK all who tried to help.

        Microsoft was the bad guy here, not the people trying to help. In over 40 years in the PC business I have never had a virus, or Microsoft update problem. This one just blew my computer away. Lucky I guess for all those years, I’ve sure fixed enough Microsoft based problems.

        But I for one THANK the posters to this site.

  52. Hello

    I’ve been struggling with this issue for over a week now with an Asus laptop. When I get to my log on screen and click on a user icon it goes in to a loop and re displays the log on screen, before the update clicking on a user would bring up the on screen keyboard which I understand is an issue. I never created a repair disk for this laptop but made one using my desktop, it’s a Windows 7 64 bit, I installed this disk in the laptop but it claimed it wasn’t compatible. I imagine the laptop is Windows 7 32 bit?

    I currently have the hard drive connected to my pc using a usb to sata kit. Anyway to correct the problem this way? Thanks for everyone’s help so far.

  53. I just had my computer in the shop since last week with login problems so I assume it was the above that caused this. Usually updates are automatic so I will need to keep your suggestions in mind if it happens again. Fortunately it is now up and running.

  54. Windows Explorer on Windows7 no longer refreshes after folder operations – have to manually refresh f5.
    e.g. add an new folder or move files, the screen doesn’t update but has done it!

    • I have had that behaviour about 60% of the time on all versions of windows from early days of W7 to W8.1 . I don’t think this or any other recent update has suddenly introduced that behaviour. I get into the habit of doing a right click on a blank part of the folder & select refresh automatically after I save an item, unless I am closing the folder

  55. Pingback:Velocity may actually make some fitment issues worse – Simmer and stir

  56. Pingback:IE Running Unexpectedly In Background. Unable To Boot To Safe Mode –

Leave a Reply

Your email address will not be published. Required fields are marked *