Jump to content
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. ×

Bilar Crais

  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

2 Neutral

About Bilar Crais

  • Birthday 11/04/1963

Contact Methods

  • Website URL
  1. That did the trick. BTW, before I knew you had a beta available, I had purchased a different product to fill in temporarily. From a company that Rhmynes with FarClock. Let me say that your product utterly destroys the competition.
  2. I don't have a "local dump" subkey for "Windows Error Reporting", whereas the tutorial you've linked to shows it there by default. However, I can try to create it. By the way, this is what's happening as the result of the crashing in Windows Error Reporting/App log: Faulting application name: explorer.exe, version: 10.0.10166.0, time stamp: 0x55976770Faulting module name: painter_x64.dll, version:, time stamp: 0x54fc14dbException code: 0xc0000005Fault offset: 0x000000000000128bFaulting process id: 0x1344Faulting application start time: 0x01d0bc1d3a6f46dcFaulting application path: C:
  3. I am running on W10 '166 x64, and when I install the beta, explore.exe crashes and relaunches repeatedly in rapid sucession. It did this on '159 as well. Anyone else?
  4. Here's the official, correct way of fixing this issue: Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2 Courtesy and credit of "The Fixer."
  5. No annoyance The only difference between the two is that version 2.6 integrates service pack 1. Either one will do, though version 1.7 will suffice.
  6. Agreed. I started keeping it because I got tired of wrestling with Windows Update. The 1.7 version has a new way to integrate the drivers; RT7 Lite puts the Nvidia drivers in a folder called CustDrivers in the Windows directory, They are installed only after you reboot the computer after installation. I prefer the old fashion way, but I guess it didn't work so well and he had to come up with an alternative method.
  7. Yes, when using RT7Lite. The only other thing I did differently is that Windows Update released a new Nvidia driver version recently, so I tried to integrate those, which I had previously been successful with. Also, Driverpacks.net had a new Nvidia driver for integration, and I tried that one too, but it also is deleted on first boot. Maybe it had nothing to do at all with the cache, but the different drivers.
  8. So why is it that if I KEEP the Winsxs cache, my integrated Nvidia drivers are deleted from the DriverStore folder? This is the first time I've ever kept the cache. I can see the driver loading on the second reboot of the installation, but when the installation completes, and it comes to the desktop, the drivers are not installed, and the integrated drivers folder is empty.
  9. Is it a genuine .ISO? As in, not been tampered with by some third party?
  10. If you have integrated SP1 with RT7 Lite, but want to clean the SP backup files before installing the image, I've prepared this guide for the DISMally challenged: This works whether you have only integrated SP1 with RT7 lite and exited the program before customizing, or after you've integrated and fully customized your image. This assumes that your freshly integrated image already resides in a folder. If you have already modified the new SP1 image with RT7 lite, deleted the folder, and made an .ISO, you can extract the .ISO into a folder. For the sake of simplicity, I suggest you rename tha
  • Create New...