If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Easeus to do backup
Just to let folks know that Easesus todo backup does not work with the
Windows 10 Cpring Creators edition. Any attempt to use the preOS or the rescue disk to restore a file will result in a blue screen referencing eukbmon.sus (an Easeus file) being in a non-page area. The only solution is to try to boot into safe mode and delete Easeus. It is necessary to use their cleanup tool to remove the eukbmon.sys file and the offending registry entries. |
Ads |
#2
|
|||
|
|||
Easeus to do backup
Howard wrote:
Just to let folks know that Easesus todo backup does not work with the Windows 10 Cpring Creators edition. Any attempt to use the preOS or the rescue disk to restore a file will result in a blue screen referencing eukbmon.sus (an Easeus file) being in a non-page area. The only solution is to try to boot into safe mode and delete Easeus. It is necessary to use their cleanup tool to remove the eukbmon.sys file and the offending registry entries. Which OS did you use for the boot image? WinPE or Linux? If WinPE, did you use use a prior Windows version for the PE image? The boot image (preOS) loads its own OS and doesn't depend on anything in the normal OS (which is quiescent while using the preOS). It's just multi-booting; however, they are using Microsoft's dual-boot scheme (to load the OS image pointing to by BCD) rather than adding an OS to the UEFI table or usurping the bootloader in the MBR's boot sector. That's why I'm wondering which WinPE image you used to build their bootable OS image. I wouldn't yet trust any Windows 10 version of WinPE. https://en.wikipedia.org/wiki/Window...on_Environment I usually try to keep the WinPE image at the same version of my main OS; else, I use a version one behind. See what happens when you build ToDo's boot image using WinPE 5.0 (Windows 8) or 3.1 (Windows 7). Use a WinPE version that works. I suspect there is nothing an earlier WinPE version cannot do to support file/partition restores that the Windows 10 version of WinPE can do. |
#3
|
|||
|
|||
Easeus to do backup
On Wed, 23 May 2018 08:47:51 -0500, VanguardLH wrotG:
Howard wrote: Just to let folks know that Easesus todo backup does not work with the Windows 10 Cpring Creators edition. Any attempt to use the preOS or the rescue disk to restore a file will result in a blue screen referencing eukbmon.sus (an Easeus file) being in a non-page area. The only solution is to try to boot into safe mode and delete Easeus. It is necessary to use their cleanup tool to remove the eukbmon.sys file and the offending registry entries. Which OS did you use for the boot image? WinPE or Linux? If WinPE, did you use use a prior Windows version for the PE image? The boot image (preOS) loads its own OS and doesn't depend on anything in the normal OS (which is quiescent while using the preOS). It's just multi-booting; however, they are using Microsoft's dual-boot scheme (to load the OS image pointing to by BCD) rather than adding an OS to the UEFI table or usurping the bootloader in the MBR's boot sector. That's why I'm wondering which WinPE image you used to build their bootable OS image. I wouldn't yet trust any Windows 10 version of WinPE. Easeus uses its own WnPE. The problem is with an Easeus file eukbmon.sys which gets a blue screen with a paging error. They sent me a file which corrected the problem when trying to use the Window 10 version of Easeus. But when trying to use the PreOS or the rescue disk they asked me to create using special instructions, the PreOS and the rescue disk destroyed my boot loader and I couldn't boot. https://en.wikipedia.org/wiki/Window...on_Environment I usually try to keep the WinPE image at the same version of my main OS; else, I use a version one behind. See what happens when you build ToDo's boot image using WinPE 5.0 (Windows 8) or 3.1 (Windows 7). Use a WinPE version that works. I suspect there is nothing an earlier WinPE version cannot do to support file/partition restores that the Windows 10 version of WinPE can do. |
#4
|
|||
|
|||
Easeus to do backup
Howard wrote:
Easeus uses its own WnPE. https://www.easeus.com/backup-utilit...able-disk.html I'm used to software that lets *me* pick which WinPE version to use on their rescue CD and dual-boot image. The problem is with an Easeus file eukbmon.sys which gets a blue screen with a paging error. They sent me a file which corrected the problem when trying to use the Window 10 version of Easeus. But when trying to use the PreOS or the rescue disk they asked me to create using special instructions, the PreOS and the rescue disk destroyed my boot loader and I couldn't boot. Using the rescue CD means using the BIOS to select the boot device, not the MBR or UEFI with their bootloaders. The PreOS uses the dual-boot scheme in Windows so, yep, MBR or UEFI was used to load the Windows bootloader which then reads the BCD to let you select which image to load but then you are already past using the bootloader. A bad driver in their own image can cause that OS to BSOD, as with any multi-booting setup, but the other OSes should still be just the same as they were. The only way I can see Easeus stepping on the MBR or UEFI bootstrap program is by using the program to step on that portion of the disk during a restore operation. Bootloaders in the MBR or UEFI don't load eukbmon.sys or any other driver. The OS must get loaded before a driver designed for that OS can load. You're already into the OS load by the time eukbmon.sys can effect anything. Has Easeus published any documention noting what you encountered? eukbmon.sys might be and probably is in their OS image for the rescue CD and preOS setups (since both use the same WinPE image generated by their program). However, that driver is also installed in the real OS because it is used by their software. A driver that is crashing will cause a BSOD in the rescue CD's OS, the preOS, and in the real OS. Drivers are kernel-mode processes so they load early. You are no longer using the bootloader(s) at that point. You are into loading the OS. If a driver keeps crashing on its load, it will keep BSODing the OS in which it gets loaded. eukbmon.sys in *not* part of WinPE. It is part of the Easeus software that gets added to the WinPE image, and into your own OS's configuration. Can you get into your normal Windows 10 instance by booting it into its safe mode? https://www.digitalcitizen.life/4-wa...ode-windows-10 Try methods 5 or 6. Method 7 would work but timing is often so fast that the keystrokes don't get registered. If you search online on "easeus eukbmon.sys crash", this has been going on for many years. If you cannot get into Windows safe mode to rename that file (so the driver cannot be found on the next *OS* boot, not when the bootloader runs in the MBR or UEFI), you could use the Windows install CD to go into recovery mode to get into console mode to use the command line. Rather than have to hunt for the install CD to use its recovery console again later, you might want to install the Recovery Console to the hard disk to use as one of the boot options (but that requires the boot sector and OS bootstrap programs work sufficiently to read the BCD to offer the dual-boot choices); see: https://support.microsoft.com/en-us/...covery-console Alternatively, use a bootable Linux distro to rename the file in the Windows partition. After renaming eukbmon.sys to, say, eukbmon.old, also rename euwatch.exe (to prevent that from running a pending backup job on startup). Then reboot whereupon the bad driver will no longer be found so it cannot be loaded which then has it crash. |
#5
|
|||
|
|||
Easeus to do backup
The only way I found to get out of the blue screen paging error fault
was to boot into safe mode, remove Easeus, and use the cleanup tool they provide to get rid of the eukbmon,sys file and other entries. Windows 10 will then boot. Upon complaint to easeus they supplied a revised installer wihcih allows installation of the product. It is then possible to use the backups to reinstall individual files. But the PreOS and the emergency disk dont work and get a blue screen. If you search "eukbmon.sys page fault" on google you willl find a lot of german users who are complaining about this issue. On Wed, 23 May 2018 21:00:58 -0500, VanguardLH wrotG: Howard wrote: Easeus uses its own WnPE. https://www.easeus.com/backup-utilit...able-disk.html I'm used to software that lets *me* pick which WinPE version to use on their rescue CD and dual-boot image. The problem is with an Easeus file eukbmon.sys which gets a blue screen with a paging error. They sent me a file which corrected the problem when trying to use the Window 10 version of Easeus. But when trying to use the PreOS or the rescue disk they asked me to create using special instructions, the PreOS and the rescue disk destroyed my boot loader and I couldn't boot. Using the rescue CD means using the BIOS to select the boot device, not the MBR or UEFI with their bootloaders. The PreOS uses the dual-boot scheme in Windows so, yep, MBR or UEFI was used to load the Windows bootloader which then reads the BCD to let you select which image to load but then you are already past using the bootloader. A bad driver in their own image can cause that OS to BSOD, as with any multi-booting setup, but the other OSes should still be just the same as they were. The only way I can see Easeus stepping on the MBR or UEFI bootstrap program is by using the program to step on that portion of the disk during a restore operation. Bootloaders in the MBR or UEFI don't load eukbmon.sys or any other driver. The OS must get loaded before a driver designed for that OS can load. You're already into the OS load by the time eukbmon.sys can effect anything. Has Easeus published any documention noting what you encountered? eukbmon.sys might be and probably is in their OS image for the rescue CD and preOS setups (since both use the same WinPE image generated by their program). However, that driver is also installed in the real OS because it is used by their software. A driver that is crashing will cause a BSOD in the rescue CD's OS, the preOS, and in the real OS. Drivers are kernel-mode processes so they load early. You are no longer using the bootloader(s) at that point. You are into loading the OS. If a driver keeps crashing on its load, it will keep BSODing the OS in which it gets loaded. eukbmon.sys in *not* part of WinPE. It is part of the Easeus software that gets added to the WinPE image, and into your own OS's configuration. Can you get into your normal Windows 10 instance by booting it into its safe mode? https://www.digitalcitizen.life/4-wa...ode-windows-10 Try methods 5 or 6. Method 7 would work but timing is often so fast that the keystrokes don't get registered. If you search online on "easeus eukbmon.sys crash", this has been going on for many years. If you cannot get into Windows safe mode to rename that file (so the driver cannot be found on the next *OS* boot, not when the bootloader runs in the MBR or UEFI), you could use the Windows install CD to go into recovery mode to get into console mode to use the command line. Rather than have to hunt for the install CD to use its recovery console again later, you might want to install the Recovery Console to the hard disk to use as one of the boot options (but that requires the boot sector and OS bootstrap programs work sufficiently to read the BCD to offer the dual-boot choices); see: https://support.microsoft.com/en-us/...covery-console Alternatively, use a bootable Linux distro to rename the file in the Windows partition. After renaming eukbmon.sys to, say, eukbmon.old, also rename euwatch.exe (to prevent that from running a pending backup job on startup). Then reboot whereupon the bad driver will no longer be found so it cannot be loaded which then has it crash. |
#6
|
|||
|
|||
Easeus to do backup
Howard wrote:
The only way I found to get out of the blue screen paging error fault was to boot into safe mode, remove Easeus, and use the cleanup tool they provide to get rid of the eukbmon,sys file and other entries. Windows 10 will then boot. Upon complaint to easeus they supplied a revised installer wihcih allows installation of the product. It is then possible to use the backups to reinstall individual files. But the PreOS and the emergency disk dont work and get a blue screen. They really need to let the *user* decide which version of WinPE to use instead of defaulting to the version 10 just because you happen to be using Windows 10. You don't need the same WinPE version as the Windows version. Hell, if it weren't for some of the network limitations, you could use Linux (which is one of the choices for the rescue boot image, well, it is in other backup products). If you search "eukbmon.sys page fault" on google you willl find a lot of german users who are complaining about this issue. A lot of users everywhere. As I recall from a prior search, I saw complaints about eukbmon.sys going back to early 2012. Just in case the problem is Easeus forgot to properly sign their driver(s) - I believe digital signing of drivers became required as of Windows 7 - you could run "sigverif.exe". Then check for any errors in the sigverif.txt log file (turn off word-wrap in Notepad). However, I suspect sigverify only checks drivers used and defined within the current instance of Windows, not in an image elsewhere, like on rescue CD or a .dat file used to hold an OS image loaded by the MS boot loader. Since you already uninstalled Easeus To Do, the eubkmon.sys should be absent so sigverify won't find it. First the code gets established and then it gets separately signed, so sometimes the 2nd step gets missed. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|