And to answer your question, yes the my book live work fine with windows 8, including smartware and wd2go for remote access. If you mean that the latest version of smartware is not recognizing the my book, try uninstalling that version and install the one that came bundled with the my book. This is utterly annoying, also given the fact that win 8 has been around since September for developers to try and test I myself have been using it on and off since then ….
Or maybe they just want win 8 costumers to say goodbye to WD given that similar products will surely soon come from MS itself, and will definetely bring more compatibility…. It seems that the supplied software is only good for Win7 and it will not work under Win8. Is there an upgrade to the software available? I have read the earlier reply but it is not correct to say the this drive will work under Win8 - it does not.
So, I would suggest you to try the following steps and check if the issue persists. Remove and reinstall all USB controllers. The issue could be if the drivers are not updated or get corrupted. So, try to install all of the Windows updates available and if issue persists, try to update the USB and mouse drivers by following the steps provided in the article mentioned below.
How to: Install and Update drivers in Windows If issue persists try the steps provided to uninstall the USB device from Device Manager, uninstall the device drivers from program list and then download the latest drivers from the manufacturer's website. Uninstall the Device from Device Manager.
Download and install the latest drivers for the USB from the manufacturer website. Hope this would help. If issue still persists post back with current status of your computer and result of proposed suggestion, we will be happy to assist you. Was this reply helpful? Yes No.
Sorry this didn't help. Thanks for your feedback. For Example you will see "Windows C " or any other partitions your computer has. It will also display other Disks Volumes , typically they do not have assigned Drive name, that is the reason, the computer can not display these Disks. Bang you would be able to see the Drives now in "This PC".
I was okay with Windows 7. But with the new Windows 10 I get a black window in the lower-right that says the drive does not work. It does offer a scan to fix it but WD does not recommend it without backing everything up on the laptop hard drive first. This, without access to the WD external drive, is impossible. The fix enables the application to run by using elevated privileges.
The fix is the equivalent of specifying requireAdministrator in an application manifest. The fix enables the application to run by using the highest available permissions. This is the equivalent of specifying highestAvailable in an application manifest.
RunAsInvoker The problem occurs when an application is not detected as requiring elevation. The fix enables the application to run by using the privileges that are associated with the creation process, without requiring elevation. This is the equivalent of specifying asInvoker in an application manifest. SessionShim The fix intercepts API calls from applications that are trying to interact with services that are running in another session, by using the terminal service name prefix Global or Local as the parameter.
At the command prompt, you can supply a list of objects to modify, separating the values by a double backslash. Or, you can choose not to include any parameters, so that all of the objects are modified. Therefore, applications that require access to Session 0 automatically fail.
SetProtocolHandler The fix registers an application as a protocol handler. You can control this fix further by typing the following command at the command prompt: Client;Protocol;App Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application.
Note: Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash. SetupCommitFileQueueIgnoreWow The problem occurs when a bit setup program fails to install because it requires bit drivers.
The fixdisables the Wow64 file system that is used by the bit editions of Windows, to prevent bit applications from accessing bit file systems during the application setup. ShimViaEAT The problem occurs when an application fails, even after applying acompatibility fix that is known to fix an issue.
Applications that use unicows. The fixapplies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion. ShowWindowIE The problem occurs when a web application experiences navigation and display issues because of the tabbing feature. The fixintercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. Sonique2 The application uses an invalid window style, which breaks in DWM.
This fix replaces the window style with a valid value. SpecificInstaller The problem occurs when an application installation file fails to be picked up by the GenericInstaller function. The fixflags the application as being an installer file for example, setup.
SpecificNonInstaller The problem occurs when an application that is not an installer and has sufficient privileges generates a false positive from the GenericInstaller function.
The fixflags the application to exclude it from detection by the GenericInstaller function. This fix resolves the issue. UIPIEnableCustomMsgs The problem occurs when an application does not properly communicate with other processes because customized Windows messages are not delivered.
The fixenables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code. You can control this fix further by typing the following command at the command prompt: MessageString1 MessageString2 Where MessageString1 and MessageString2 reflect the message strings that can pass.
Note: Multiple message strings must be separated by spaces. UIPIEnableStandardMsgs The problem occurs when an application does not communicate properly with other processes because standard Windows messages are not delivered. The fixenables standard Windows messages to pass through to the current process from a lower Desktop integrity level.
This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code. You can control this fix further by typing the following command at the command prompt: Where reflects the first message ID, reflects the second message ID, and reflects the third message ID that can pass.
Note: Multiple messages can be separated by spaces. VirtualizeDeleteFileLayer The fix virtualizes DeleteFile operations for applications that try to delete protected files. VirtualRegistry The problem is indicated when a Component failed to be located error message displays when an application is started. The fixenables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on.
For more detailed information about this application fix, see Using the VirtualRegistry Fix. VirtualizeDeleteFile The problem occurs when several error messages display and the application cannot delete files. The fixmakes the application's DeleteFile function call a virtual call in an effort to remedy the UAC and file virtualization issues that were introduced with Windows Vista.
This fix also links other file APIs for example, GetFileAttributes to ensure that the virtualization of the file is deleted. The use of HKCU is preferred if an application is not elevated and is ignored if the application is elevated.
You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix. WaveOutIgnoreBadFormat This problem is indicated by an error message that states: Unable to initialize sound device from your audio driver; the application then closes.
The fixenables the application to ignore the format error and continue to function properly. WinxxRTMVersionLie The problem occurs when an application fails because it does not find the correct version number for the required Windows operating system. All version lie compatibility fixes address the issue whereby an application fails to function because it is checking for, but not finding, a specific version of the operating system. The version lie fix returns the appropriate operating system version information.
For example, the VistaRTMVersionLie returns the Windows Vista version information to the application, regardless of the actual operating system version that is running on the computer. Wing32SystoSys32 The problem is indicated by an error message that states that the WinG library was not properly installed. The fixdetects whether the WinG32 library exists in the correct directory.
Important: The application must have Administrator privileges for this fix to work. The fixforces the application to follow these steps: Open the Compatibility Administrator, and then select None for Operating System Mode. Type vbrun Save the custom database. You can control this fix further by typing the following command at the command prompt: Component1.
WRPMitigation The problem is indicated when an access denied error message displays when the application tries to access a protected operating system resource by using more than read-only access. The fixemulates the successful authentication and modification of file and registry APIs, so that the application can continue. WRPRegDeleteKey The problem is indicated by an access denied error message that displays when the application tries to delete a registry key.
The fixverifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process. Compatibility Modes The following table lists the known compatibility modes. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article. This layer aggregates all the blt operations and improves performance. This layer mitigates applications that exhibit graphical corruption in full screen mode. This fix repairs applications that use GDI and that work in 8-bit color mode.
The application is forced to repaint its window on RealizePalette. This problem occurs when InstallShield creates installers and uninstallers that fail to complete and that generate error messages or warnings. This fix is indicated when an application fails to start. This problem occurs when an application's installer must run in elevated mode and depends on the HKCU settings that are provided for other users.
The problem is indicated by an access violation error message that displays and when the application fails when you select or crop an image.
The problem is indicated when an application tries to write files to the hard disk and is denied access or receives a file not found or path not found error message. This problem occurs when an uninstalled application leaves behind files, directories, and links.
This problem occurs when you start an executable. This fix instructs DWM to not render the non-client area, thereby forcing the application to do its own NC rendering. The problem is indicated when an application tries to install a service that has a dependency on a deprecated service.
The problem occurs when some objects are not drawn or object artifacts remain on the screen in an application. The problem is indicated when an application fades animation, buttons, or other controls do not function properly.
The problem is indicated by an application that behaves unpredictably when it tries to detect and use the correct Windows settings.
0コメント