Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


WalksInSilence

Member
  • Content Count

    78
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by WalksInSilence

  1. I'm not sure what the problem might be although it obviously concerns that igdumd64.dll. It is apparently an Intel Graphics Driver DLL - do you have problems launching any of the other MS Win7 games? If so it might be problem with that DLL or the driver itself which will have to be addressed. I can't give any advice on that. The games which come with WIn7 are located in C:\Program Files > Microsoft Games so I'd go to that folder and click on the Solitaire EXE to see if it works from there. If it does then its probably a shortcut/start menu (Games) shortcut issue and you just need to replace it/them. Do you have the original installer you used or do you mean you just had to enabled the Win7 Games 'feature' from the Control Panel. That's normal; for whatever reason the Win7 games are not enabled by default. If it is still not working then I'd run system file checker and then chkdsk . I doubt either will fix the problem but it might worth trying. Do you have the original Win7 installer disc? If so you may be able to find the games folder on there and get Solitaire out of that and simply replace the existing copy. I thought it might be possible to use a Win7 games installer for Win10 download to get the game's folder and EXE for Solitaire. Whilst it is possible to extract it, actually quite easy, I've tried several things and couldn't get it to launch on a Win7 64bit Pro PC. So it appears you need someone to share an original Win7 version of the particular game's folder/EXE because the only other solution I've seen suggested is to reinstall Windows 7 completely. Of course there is no guarantee doing any of that will fix the problem if it is a graphics driver or DLL problem.
  2. The easiest solution is to run Win7 on a virtual machine. It should resolve most if not all of the driver or other problems.
  3. You definitely do need to check your RAM. A loss of speed like that sounds like a module may have failed or something is hogging the memory as others here have suggested. An anti-virus program perhaps (AVAST?). When we were forced to dump the ideal for this purpose MSE with XP installations I had to find a suitable working alternative for XP on a VM. I settled for a claimed lightweight one but I immediately noticed XP on the VM was much slower to boot and things like browsers and even some system tools would launch, initially, with a significant delay. Shutdown was also delayed. I would not use a recent FF version with XP anyway but as somebody who had a Dell XP laptop with limited RAM support (max 1GB in two 516MB modules but would sometimes work with 2x1GB ones) I know just how much how much of an effect losing one stick can have. With XP on the VM with 1GB of allocated RAM it works well with a pre-v57 FF version although I very rarely use it online now anyway. However the VM is on a SSD so that probably helps. Anything running off a HDD is going to be slower initially but 10 minutes to launch FF - there's something unnatural going on.
  4. My suggestion would be to install XP on a virtual machine. If the laptop has plenty of RAM and decent enough CPU it should be doable.
  5. Creating a backup image was what I meant and programs like EaseUS Todo allow you to do that for individual folders without having to go through all the permissions hoops required just to be able to copy the SVI file folder. But, as said, I've never had the guts to try importing that back in full or just adding the backed up restore points from it. But if it did work you could create a scheduled task for backing up the SVI to run at boot or every three days. But I really do not know if any of this is possible or practical - just floating the possibility. For me manually creating restore points seems like the best solution but I agree it should be possible to automate that to do as you want.
  6. I was going to say something about the frequency too but that does depended on how much space you've allocated to restore points. Having a smallish 120GB SSD primary drive I reserve about 8% which in practice means about 10GB of space and 7 or 8 restore points. I put in a manual restore point every week and delete those if more than a month old but only if I've had no problem. That saved me recently; I had this weird issue I won't bore you with but I couldn't find a solution and the web site of the program involved is now just an archive with no mention of similar issues. I worked my way back through the 6 restore points I had and it was only using the last one, six weeks old, that fixed whatever the problem was. If I'd been creating restore points every three days I'd have nothing but month old restore points and how I would have fixed the problem I've no idea as I'd tried every other method I could think of to no effect. What I really wish was that there was a restore point save option either provided or as a third party tool. Whilst you can backup the Windows System Volume Information folder which contains, amongst other things, the restore points, I've never had the confidence to risk testing if they actually work months later. Instead I content myself backing up the registry once a month and hope I never have to use it. So far so good.
  7. Just looked into this a bit more and I found this :- "Windows controls the creation of automatic restore points based on a frequency setting to help limit the number of restore points that get saved. By default, Windows won’t create an automatic restore point if another restore point has been created in the last 24 hours." That I did not know. Could it be the explanation? Apparently changing the Registry's Restore Point frequency setting to off may allow you to do what you want. The quote is from 'The How To Geek' web site which also details how to do that. I've always found it a good source of advice on a lot of niche subjects like this:- https://www.howtogeek.com/278388/how-to-make-windows-automatically-create-a-system-restore-point-at-startup/
  8. I use the 'Check for updates but let me choose...............etc" and do have that recommended updates box ticked too. Consequently I can't blame anything other than my own casualness for downloading and installing it on the PC concerned.
  9. Unusually today there was a notification in my system tray about an important Windows update. It turned out to be Edge, absentmindedly I forgot I don't have Edge installed on the particular PC I was using and clicked to install the 'update'. All I can say is I'm very thankful for System Restore. The bloody arrogant thing installed Edge and actually launched on top of my desktop after boot and with, initially, no way out, I used Task Manager to kill it. With System Restore and other tools I've since removed as much evidence that it was on the machine as I've been able to find and hidden the update when it was 'offered' again. The 'update' is still shown as successfully installed under Updates but if you go to installed updates it is not there so, presumably, that just means it was successfully installed at the time and that's all. In short - when offered an 'important' update check before you install it.
  10. My advice is do not rely on Windows to make restore points. Do it yourself before installing new software and/or on a weekly basis. I do that as part of my regular PC maintenance schedule. The system created ones seem to be made rather randomly whatever settings you use but I think that if you check there are by default multiple triggers. On my PC, which I do not remember changing from default, it is set to create new ones on start up and at 0.00 daily but only if this criteria applies:- "By default, Windows will automatically create system restore point when new software is installed*, when new Windows updates installed, and when a driver is installed. Besides, Windows 7 will create a system restore point automatically if no other restore points exist in 7 days." Task Scheduler checks at those specified times but other conditions apply too so check under the Conditions tab what those are. My guess is that this is the 'problem' - if the PC is not idle at those times a restore point won't be create then either. The one that does seem to apply irrespective of the other triggers is the >7 day one. There is also the possibility you have not assigned enough space for the restore points. Key restore points can be 2+GB and most are around 1GB so if you've only allocated say 6GB you're only going to have 3 or 4 restore points available at any time before they're deleted. The default Windows 7 allocated space is 5% so if you're using a relative small primary drive SSD (120GB or less) that 5% so it could easily be you just have 6GB for restore points. I use 10% and currently have 5 restore points, none of them system created. * I do not think that includes portable software and it does not include updates to already installed programs. That's why I put in a manual restore point before updating anything.
  11. So it is possible to update Win7 itself using the MS catalogue - I did not realise that could still be done. I've never used automatic updates with Win7 and I'd assumed all I'd get from now on was notifications about non-system updates like MS Net Framework etc.
  12. Yes but we're past Win7 EOL and MS Support. That was supposed to end on 14th January with the final rollup. The black wallpaper problem some people have experienced, apparently caused by something in that final rollup forced MS to issue a patch, post support cut off date. You could get the patch as an optional download but at some point they started offering a new rollup Preview instead with the support pages stating:- "This non-security update includes improvements and fixes that were a part of KB4534310* (released January 14, 2020) and also includes these new quality improvements as a preview of the next Monthly Rollup update." What next Monthly Rollup update? I'm not signed up for the Win7 ESR so why am I being offered a Preview of something I'm not going to get? * I installed that almost a month ago, and it had issues for me but not the black wallpaper one so I did not install the later patch when it was first offered as an optional update. The Preview makes it appear they may actually be going to issue a post EOL Monthly Rollup for (all?) WIn7 machines.
  13. Yes, that is one of my pet general forum use dislikes: when somebody asks a question, gets help and then later posts some variation on:- without actually explaining exactly how they resolved the problem. So many times you look for answer to a particular question online and find a thread in some long dead or now barely used forum which is about just what you wanted to know and the thread is abruptly ended by a post like that. Frustrating and a wee bit selfish.
  14. I think driver support on more recent systems won't be an issue at present but if somebody comes here in the not too distant future wanting to do the same thing on a then contemporary PC it could be. I had problems with Windows XP in 2016 which I originally wanted to work in dual boot with Win7. It was actually the lack of a specific MB driver required to use XP with SATA HDDs, the SATA Controller driver, that caused the biggest trouble. When I bought the MB the listing said it was XP compatible. However when I finally started building the PC I discovered too late the version I had only supported Win7 and 8. By luck I guess all the other important drivers did still work with XP, it was just that SATA Controller one that did not. I eventually found a generic XP SATA Controller driver for the MB and managed to install it without a full XP re-install. Under XP the Device Manager says it is working but it is not. I still have to swap to legacy IDE mode in the BIOS/UEFI then reboot and choose the XP OS boot drive to get it to launch and go through the reverse process to get back to Win7. Utter pain and why I now use XP on a VM instead. That sort of thing and the undoubted inexorable increase in the ending of important software support for Win7 will, slowly, reduce its use as a primary OS and its overall viability.
  15. Interestingly there is an "Optional" MS provided update for Win7 users this month: apparently the final Monthly Rollup introduced an annoying bug on some systems which renders the wallpaper you're using as all black. Hasn't affected either of my two Win7 PCs; one uses a custom wallpaper and the other a MS wallpaper that came included with Win7 so no point in installing the update. Anyone here experienced this bug? EDIT A bit weird, I'm now being offered as an optional update:- 2020-01 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4539601) Download size: 314.4 MB You may need to restart your computer for this update to take effect. Update type: Optional This apparently includes the stuff that was in the 14th January KB4534310 'final' Win7 monthly rollup which I do have installed but also includes the black wallpaper fix too. Whether MS are going to release the whole Preview content as an additional post EOL update or revert back to just providing the optional wallpaper fix will be interesting to see. But why offer the full Preview to those without the extended licence who have KB4534310 installed if they are only going to get the wall paper fix?
  16. Google and you'll find find plenty of advice for such circumstances. Apparently if you have not set an Administrator password you can start in Safe Mode and try logging on with the Administration password field blank. Safe Mode with Command Prompt offers another route too.
  17. RE: my niche issue with the January updates mentioned on one Win 7 64bit PC. Put in a restore point and re-downloaded each update separately and tested the system after each with a second reboot. All now seems good - the encrypted volume type affected is still opening normally now with all three updates installed. What caused the problem? No idea but it is the first Windows update that has caused trouble with other programs which I've had in years. "Telemetry gathering" annoyances excluded.
  18. Oh oh! Niche, very niche issue has appeared on one of my two Win7 64bit PCs since the January MS update installs. I did not notice it until yesterday when I tried to open an encrypted volume made by a particular free encrypted volume program. In fact I have such volumes each on the three main drives SDD/2xHDDs I use. They open with a password and I found that when I opened any one of those, on whatever drive, I had an error message I'd not seen before about a "General problem opening the volume". When I closed it and re-entered the password it opened perfectly. Likewise the other volumes too. But restart or from cold boot this behaviour persists first time the first volume is opened. Utterly consistent but it should not be happening. Initial thought was a SSD/HDD issue but when I found the behaviour was system wide I ran CHKDSK on every drive and they all came through perfectly. System File Checker found no problem on the primary drive either. Full system scans with AV/Anti-Spyware/Malware/Adware produced nothing amiss. I tried:- 1). Creating new encrypted volumes - same problem. 2). Thorough uninstall of the encryption program using Revo and then clean re-install - same problem. Eventually I decided to use a pre-Windows January update Restore Point (11.01.20) to roll the system back. A number of other programs I'd updated since then were shown as likely to be affected along with the Windows update but I took the risk. All went perfectly apparently, took some time but it eventually rebooted OK. Ran several tests on the encrypted volumes, restarting the PC again twice just to confirm it and everything back to normal. Now I've updated all those other programs, about a dozen, updated since the Restore Point date. Restarted the PC at various points and the encrypt volume behaviour opening is still back to normal. So not any of those other programs can be the culprit. All that is left now are those three MS January updates mentioned earlier:- KB4534310: Windows January Rollup. KB4536952: Service stack update. KB4535102: 2020-01 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 It has to be one of them that caused the problem and my money is on the .NET Framework KB4535102. I'm going to try each one in order but wait and see if anyone else reports anything peculiar. However here's the thing I do not understand: my other Win7 64bit PC was updated exactly the same way earlier, in fact I'd updated that first, and has experienced no similar problem. I've tested and restarted it multiple times. I almost wished it had produced the same result because now I'm wondering what is on this PC that has made this minor but unwanted behaviour unique to it.
  19. Has anyone here in this thread actually mentioned it? I've been back over the posts and if someone did it passed me by. That ^ actually does more to advertise the tool than anything else I've seen here. Perhaps I'm misinterpreting the intended purpose of the post.
  20. Had a nag from MS today just after boot with a warning blue screen about Win7 being out of support. Thankfully an option provided not to be reminded again. Checked my scheduled tasks and nothing new there, all customer experience options disabled and then I noticed in the task tray that there are updates available (I'm set to auto-check for updates but choose if/when to install). So I guess they added the message to the update tasks. Hate the fact the message could just override everything else I was doing at the time and was not just made a discrete addition to the Windows updates. Interestingly, presumably the final monthly Win7 Quality Rollup, KB4534310 is one of the updates. The other two are a .NET Framework update and the usual Malicious Software Removal Tool. Checked the main update at MS and they have added an IMPORTANT message about the EOL:- "IMPORTANT Starting on January 15, 2020, a full-screen notification will appear that describes the risk of continuing to use Windows 7 Service Pack 1 after it reaches end of support on January 14, 2020. The notification will remain on the screen until you interact with it. This notification will only appear on the following editions of Windows 7 Service Pack 1: Starter. Home Basic. Home Premium. Professional. If you have purchased the Extended Security Update (ESU), the notification will not appear. For more information, see How to get Extended Security Updates for eligible Windows devices and Lifecycle FAQ-Extended Security Updates. Ultimate. Note The notification will not appear on domain-joined machines or machines in kiosk mode." EDIT Had a later update offered too: another servicing stack update:- 2020-01 Servicing Stack Update for Windows 7 for x64-based Systems KB4536952. Like the earlier two it downloaded and installed without any issues, so far.
  21. The fact you call it an app suggests you're posting in the wrong forum. This is the Windows 7 forum, sounds as if you're using Windows 10. You tried uninstalling Facebook? Exactly how did you do this? I would not trust the Windows uninstall tool to make a good job of it whatever the OS. Always use a purposed designed uninstaller like Revo Uninstaller or BCUninstaller. If you try Revo now you might get lucky if enough of the program remains but BCUninstaller is sometimes better if you've already partially uninstalled a program. TIP: before uninstalling/installing anything always put in a restore point. Revo does this by default.
  22. I really just mentioned the Process Hacker 2 issue as an aside. I did not think that the Windows Malicious Software Removal Tool possibly deleting PH2 is directly or otherwise related to the OP's problem. I still don't but, apparently, WMSRT itself maybe involved.......................................................... Mcinwwl ^^ link is not about the December updates but a report about a problem with last month's (November) stack update KB 4523206 which seems to have caused problem for some users as well. If you follow the links from AskWoody the WMSRT (MSRT = Malicious Software Removal Tool) is being blamed for some of the November update issues. Not for Win7 users specifically but still possibly relevant. https://social.technet.microsoft.com/Forums/en-US/d1a9bf15-99e9-458f-b942-e387308ad1a6/windows-server-2012-stuck-in-reboot-loop-8220configuring-updates-stage-2-of-4quot?forum=winserver8gen The solution for that problem if encountered seems to be booting into Safe Mode then rebooting normally. Maybe I dodged a bullet by not installing WMSRT this and last month as I've just checked and for some reason the last WMSRT shown installed on either of my Win7 PCs is the October one. Could be I've been freakishly lucky.
  23. I've not had any problem with the December updates on either of my two Win7 64bit machines. I was offered three 'important' updates initially: KB4530734 (Monthly QR), KB4533095 (.NET Framework) and the usual Windows Malicious Software Removal Tool (WMSR Tool). I only installed the first two late on the 11th December 2019. It made two PC restarts as is fairly normal for any updates that include .NET Framework ones. That was the only thing of note. The WMSR Tool I normally install without thinking about it but this month I've had a run in with MS over the anti-virus definitions used by MSE and Defender which out of the blue started reporting the third party system monitoring tool: Process Hacker 2 (PH2) as a high threat. I guessed the WMSR Tool might take it upon itself to try to remove PH2 too so I hid the update and won't use it ever again. After I'd installed the first two updates successfully I was surprised to get an immediate, small additional 'important' update offered: KB4531786 (Stack Update). That installed successfully* without a required restart but I noticed next day on cold boot that I had a "...configuring your system..." message, usually present when Windows updates are being installed, before the PC booted to the login screen. Also soon after the boot my system fans spun up and, ironically using PH2, it reported as I expected high CPU use caused by a Windows Trusted Module Installer process running. That is typical after any Windows updates and it stopped, as usual, after a few minutes. However I was suspicious so I checked all the usual places for MS having sneaked a telemetry gathering scheduled task onto my PC but nothing was found and I've had no indications of anything amiss since. BTW I did check before those Windows monthly updates installs, as I've done for years now, for reports of problems. After waiting over 24hrs there were none so I was happy to go ahead and do it. However this report of trouble here is not the first I've come across since:- https://appuals.com/kb4530734-causes-reboot-loop/ I should mention that long ago I'd opted out of the MS "....experience...." reporting and disabled three MS telemetry gathering tasks they still tried to foist on me. As a result I've not had prompts about the Win7 EOS since. Whether there is any connection between this and the problems reported by other I have no idea but I thought I should add this information in case it is relevant. * I should have checked before install but assumed the stack update was a normal part of the monthly updates and therefore safe but only later did I look for information about it. I was surprised it suggested installing it prior to any of the cumulative monthly updates! It was not being offered before I installed those other two so there was something odd going on. Could it have been a quick release fix for these reported problems? Why my two Win7 PCs have had no problem with KB4530734 I won't guess, but I provide the information I have in the hope it might help identify the cause of the problem. My thought is that if the stack update was a quick fix it might be worth trying installing that first manually before trying to install the KB4530734 Monthly QR again. EDIT Found this later which suggests you should have two other updates installed first apart from KB4530734: KB4490628 and KB4474419. I've just checked and I have both of these too. So if you do not have them, again, install all three first.
  24. Thanks for that. BTW I've corrected my original post for a typo I noticed. Of course it should have said ".....does not exactly....." rather than "That article does exactly say that - the assumption is it will but until MS unequivocally say that I won't believe it..." I've also corrected the grammar slightly.
×
×
  • Create New...