Jump to content

Bilar Crais

  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Bilar Crais

  • Birthday 11/04/1963

Contact Methods

  • Website URL

Bilar Crais's Achievements



  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:\Windows\explorer.exeFaulting module path: C:\Windows\System32\painter_x64.dllReport Id: 27cbbb8a-26ab-4ac7-85ac-4abc73d9400dFaulting package full name:Faulting package-relative application ID:Is that at all helpful? Still happens with beta 3.
  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 that folder to what I've used in the DISM command lines later on in this tutorial; Rename your RT7 image folder "W7SP1." Let's make another folder called "W7temp." Reboot, and after your BIOS posts, hit the F8 key and choose "Repair Your Computer." You'll have to be quick on the draw here; your window of opportunity is pretty slim to hit F8. Once the the recovery console has loaded, select the command prompt option from the list of recovery tools. Now let's mount the image. If you've used RT7 Lite to integrate, no matter what version of Windows you chose, (Home, Ultimate, etc.) the index number will be 1, as shown below. It's hard telling what drive letter you'll need to use in the command lines...my image files resided in my "D" drive, but in the recovery console, it became the "F" drive. I just hunted around by guessing the drive letter and typing E:\DIR and F:\DIR etc., until I found the correct drive. Type the following, assuming that your RT7 image resides in E:\W7SP1. DISM /Mount-Wim /WimFile:E:\W7SP1\sources\install.wim /index:1 /MountDir:E:\W7temp Once the image has successfully mounted, we'll clean up the SP1 backup files: DISM /image:E:\W7temp /cleanup-Image /spsuperseded DISM may report that there might not be enough disk space for the "scratch file" to perform the operation, but I found it safe to ignore this. After DISM reports that the backup files have been successfully cleaned up, you can unmount and commit the changes to your original RT7 Lite image: DISM/Unmount-Wim /MountDir:E:\W7temp /commit After the operation is complete, you may reboot. Voila! Now when you want to install the image, fire up RT7 Lite and point it to the newly cleaned folder and select no options except for the "ISO Bootable." Once the image is loaded, make a bootable image as per usual and burn to your medium of choice. May I suggest that you print these instructions before rebooting, so that once you're in the recovery console, you can refer to the command lines. Good Luck!
  • Create New...