Applies ToWindows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard Windows Server 2008 R2 Web Edition
Symptoms
Consider the following scenario:
-
You enable BitLocker Drive Encryption on a USB storage device that is connected to a Windows 7-based or a Windows Server 2008 R2-based computer.
-
When you run BitLocker To Go on the USB storage device, one of the following situations occurs and leads to an NTFS unexpected shutdown (also known as a dirty shutdown):
-
You disconnect the USB device without ejecting it.
-
The computer encounters a hard restart or shutdown, or encounters a power failure.
-
In this scenario, the USB storage device cannot be recognized or mounted on the computer. Additionally, when you run the Manage-bde.exe command on the removable storage device, the following error message is received:
ERROR: An error occurred (code 0x80070020):The process cannot access the file because it is being used by another process.
Cause
This issue occurs because the virtualized boot block on the storage is created at a random location. Therefore, the virtualized boot block is overwritten by other files incorrectly.
Resolution
Update information
How to obtain this update
Microsoft Update
This update is available from the Windows Update website.
Microsoft Download Center
The following files are available for download from the Microsoft Download Center:
|
Operating system |
Update |
|---|---|
|
All supported x86-based versions of Windows 7 |
Download the update package now. |
|
All supported x64-based versions of Windows 7 |
Download the update package now. |
|
All supported x64-based versions of Windows Server 2008 R2 |
Download the update package now. |
|
All supported IA-64-based versions of Windows Server 2008 R2 |
Download the update package now. |
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
-
Windows 7
-
Windows 7 Service Pack 1 (SP1)
-
Windows Server 2008 R2
-
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760 0.16xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760 0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760 1.18xxx
Windows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760 1.22xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Dumpfve.sys |
6.1.7600.16385 |
55,584 |
14-Jul-2009 |
01:17 |
x86 |
|
Fvevol.sys |
6.1.7600.17221 |
195,816 |
24-Jan-2013 |
04:51 |
x86 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,584 |
14-Jul-2009 |
01:17 |
x86 |
|
Fvevol.sys |
6.1.7600.21432 |
196,328 |
24-Jan-2013 |
04:53 |
x86 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,584 |
14-Jul-2009 |
01:17 |
x86 |
|
Fvevol.sys |
6.1.7601.18062 |
196,328 |
24-Jan-2013 |
04:47 |
x86 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,584 |
14-Jul-2009 |
01:17 |
x86 |
|
Fvevol.sys |
6.1.7601.22230 |
196,328 |
24-Jan-2013 |
04:28 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Dumpfve.sys |
6.1.7600.16385 |
55,128 |
14-Jul-2009 |
01:43 |
x64 |
|
Fvevol.sys |
6.1.7600.17221 |
223,752 |
24-Jan-2013 |
05:41 |
x64 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,128 |
14-Jul-2009 |
01:43 |
x64 |
|
Fvevol.sys |
6.1.7600.21432 |
223,752 |
24-Jan-2013 |
05:41 |
x64 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,128 |
14-Jul-2009 |
01:43 |
x64 |
|
Fvevol.sys |
6.1.7601.18062 |
223,752 |
24-Jan-2013 |
06:01 |
x64 |
|
Dumpfve.sys |
6.1.7600.16385 |
55,128 |
14-Jul-2009 |
01:43 |
x64 |
|
Fvevol.sys |
6.1.7601.22230 |
223,768 |
24-Jan-2013 |
05:28 |
x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Dumpfve.sys |
6.1.7600.16385 |
82,248 |
14-Jul-2009 |
01:52 |
IA-64 |
|
Fvevol.sys |
6.1.7600.17221 |
483,552 |
24-Jan-2013 |
04:52 |
IA-64 |
|
Dumpfve.sys |
6.1.7600.16385 |
82,248 |
14-Jul-2009 |
01:52 |
IA-64 |
|
Fvevol.sys |
6.1.7600.21432 |
484,064 |
24-Jan-2013 |
04:50 |
IA-64 |
|
Dumpfve.sys |
6.1.7600.16385 |
82,248 |
14-Jul-2009 |
01:52 |
IA-64 |
|
Fvevol.sys |
6.1.7601.18062 |
484,080 |
24-Jan-2013 |
04:41 |
IA-64 |
|
Dumpfve.sys |
6.1.7600.16385 |
82,248 |
14-Jul-2009 |
01:52 |
IA-64 |
|
Fvevol.sys |
6.1.7601.22230 |
484,064 |
24-Jan-2013 |
04:32 |
IA-64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File name |
X86_0e6ef9db05314fefc2dbcdfe668474b1_31bf3856ad364e35_6.1.7601.22230_none_b1a4970369362aa3.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
X86_2a6b39c5403a13d59b4c33d7de1cce8d_31bf3856ad364e35_6.1.7600.17221_none_75e1799c0df7b7f0.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
X86_640ee2fe98bc32065df3331a6b5e87e1_31bf3856ad364e35_6.1.7601.18062_none_61369a388def277c.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
X86_66d258cacdab0bf86057f077ddb0ed8a_31bf3856ad364e35_6.1.7600.21432_none_a94ff2d3d4f02282.manifest |
|
File version |
Not applicable |
|
File size |
714 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.17221_none_2e97935141145286.manifest |
|
File version |
Not applicable |
|
File size |
35,383 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:52 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.21432_none_2f1762605a3924bf.manifest |
|
File version |
Not applicable |
|
File size |
35,383 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:52 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.18062_none_3053b0f13e5a478d.manifest |
|
File version |
Not applicable |
|
File size |
35,383 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:52 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.22230_none_30fbbed257615dfd.manifest |
|
File version |
Not applicable |
|
File size |
35,383 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:52 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
Amd64_08ae60542d6498c835fcb14b98629223_31bf3856ad364e35_6.1.7600.21432_none_bd57445a838be289.manifest |
|
File version |
Not applicable |
|
File size |
718 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Amd64_1b1a122ae4155daceb8549a97531a576_31bf3856ad364e35_6.1.7601.18062_none_87494051e6d620d0.manifest |
|
File version |
Not applicable |
|
File size |
718 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Amd64_b0eb20980b94ea6ded98b03dfbc9e855_31bf3856ad364e35_6.1.7600.17221_none_4dfa9242cf8f803b.manifest |
|
File version |
Not applicable |
|
File size |
718 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Amd64_cdec8e4c241d347be214eea8a628418b_31bf3856ad364e35_6.1.7601.22230_none_c288eaaba7849758.manifest |
|
File version |
Not applicable |
|
File size |
718 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.17221_none_8ab62ed4f971c3bc.manifest |
|
File version |
Not applicable |
|
File size |
35,387 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:55 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.21432_none_8b35fde4129695f5.manifest |
|
File version |
Not applicable |
|
File size |
35,387 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:55 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.18062_none_8c724c74f6b7b8c3.manifest |
|
File version |
Not applicable |
|
File size |
35,387 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:55 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.22230_none_8d1a5a560fbecf33.manifest |
|
File version |
Not applicable |
|
File size |
35,387 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:55 |
|
Platform |
Not applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_368d1d57e928529bd03338f2c26c5558_31bf3856ad364e35_6.1.7601.18062_none_1428a98c48a5ba4d.manifest |
|
File version |
Not applicable |
|
File size |
716 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_a945d780d0c1bd63ab09aa1bfa0b0251_31bf3856ad364e35_6.1.7601.22230_none_7ef15710eafb9bb6.manifest |
|
File version |
Not applicable |
|
File size |
716 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_ca33786ff57340bdeede57f0732ffb65_31bf3856ad364e35_6.1.7600.17221_none_c15f360034003294.manifest |
|
File version |
Not applicable |
|
File size |
716 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_f582916cd4648777de25d7788d71ad45_31bf3856ad364e35_6.1.7600.21432_none_1993a278fe505c7c.manifest |
|
File version |
Not applicable |
|
File size |
716 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.17221_none_2e99374741125b82.manifest |
|
File version |
Not applicable |
|
File size |
35,385 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7600.21432_none_2f1906565a372dbb.manifest |
|
File version |
Not applicable |
|
File size |
35,385 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.18062_none_305554e73e585089.manifest |
|
File version |
Not applicable |
|
File size |
35,385 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
|
File name |
Ia64_microsoft-windows-s..tartup-filterdriver_31bf3856ad364e35_6.1.7601.22230_none_30fd62c8575f66f9.manifest |
|
File version |
Not applicable |
|
File size |
35,385 |
|
Date (UTC) |
24-Jan-2013 |
|
Time (UTC) |
22:49 |
|
Platform |
Not applicable |
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Проблема
Рассмотрим следующий сценарий:
- Вы включаете шифрование диска BitLocker на USB-накопителе, подключенном к компьютеру под управлением Windows 7 или Windows Server 2008 R2.
- При запуске BitLocker To Go на запоминающем устройстве USB, возникает одна из следующих ситуаций и ведет к непредвиденному завершению работы NTFS (неправильное отключение):
- Вы отключаете USB-устройство без его извлечения.
- Компьютер обнаруживает жесткую перезагрузку или завершение работы при обнаружении сбоя питания.
В этом случае USB-накопитель не распознается или не монтируется на компьютере. Кроме того, при выполнении команды Manage-bde.exe на съемном запоминающем устройстве выводится следующее сообщение об ошибке:
Ошибка: Произошла ошибка (код 0x80070020): Процесс не может получить доступ к файлу, так как это файл занят другим процессом.
Причина
Эта проблема возникает, поскольку виртуальный загрузочный блок в хранилище создается в случайном местоположении. Таким образом, виртуальный загрузочный блок перезаписывается другими файлами неправильно.
Пробегав по граблям вместе с вендором, выдаю кбшку. Если испытываете подобные проблему- обновляйтесь.
No USB devices working in Windows Server 2008 R2
Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar
With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under cc by-sa 3.0 | Music: https://www.bensound.com/royalty-free-music | Images: https://stocksnap.io/license & others | With thanks to user Tomin Jacob (https://superuser.com/users/357168), user Linef4ult (https://superuser.com/users/321646), user Hoermi (https://superuser.com/users/947455), user harrymc (https://superuser.com/users/8672), user Fergus (https://superuser.com/users/29347), user Deborah (https://superuser.com/users/614205), user BlueBerry – Vignesh4303 (https://superuser.com/users/148414), and the Stack Exchange Network (http://superuser.com/questions/980563). Trademarks are property of their respective owners. Disclaimer: All information is provided “AS IS” without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com.
source
windows server
Topic: Windows Server 2008 r2 not recognizing USB drive (Read 5192 times)
I can’t seem to get Windows Server 2008 r2 to recognize my Buffalo USB drive.� The drive is neary full and i want to transfer the files from it to the server.� I do NOT want to format the drive for first time use or reset the encrypted password.� This has already been done from another computer.� Just need to mount the drive and run the secure lock program (which is installed on the server) to copy the files.
�
Model is :HD-CXT2.0TU2
Firmware is: REV_0.50\00101007000D17C00&0 (I think)
�
Anyone have similiar issues?
�
�
Logged
Figured it out.� Installed Windows updates and rebooted the server.� Finds the drive now.�
Logged
Hello Guys
�
Buffalo USB drive is not detecting on Windows 2008 R2 Server even though there is no Open windows Update on the server ,
�
is anything we need to�modify the registry ???
�
if anybody has answer it will be more helpful
�
Cheers ,
Pramod �
�
Logged
pramodkr wrote:
Hello Guys
�
Buffalo USB drive is not detecting on Windows 2008 R2 Server even though there is no Open windows Update on the server ,
�
is anything we need to�modify the registry ???
�
if anybody has answer it will be more helpful
�
Cheers ,
Pramod �
�
Might help if you post the model number :-/ My physic powers aren’t what they used to be!
Logged
PM me for TFTP / Boot Images / Recovery files LSRecovery.exe file.
Having network issues? Drop me an email: info@interwebsireland.com and we will get it fixed!
Have i helped you? Buy me a coffee as a thanks!
https://buymeacoffee.com/buffalodavo
USB device is not being recognized in Windows Server 2008
Hello,
We have been facing this issue of 1 or 2 TB USB hard drive not getting detected on various Windows 2008 servers, once we reboot the USB hard drive gets recognized in My Computer.
Is there a patch for this issue, any solution would be appreciated.
Thank You, Anand
June 15th, 2011 3:53pm
Hi,
I would like to confirm that if all the TB USB drives cannot be recognized normally?
Please update to Windows Server 2008 Service Pack 2 and install the later updates. In addition, please also update BIOSs, motherboard chipset drivers
and USB drive firmware.
If it does not work, please perform the following steps to reinstall USB controllers.
Reinstall USB controllers
===========================
Use the Mouse
=============
First, please disconnect all USB devices and then perform the following steps:
1. Click «Start», type in Device Manager the Search bar and press «Enter». Click Continue if necessary.
2. In Device Manager, double click to expand «Universal Serial Bus controllers», right click on the «Host Controller», click «Uninstall» and click «OK».
3. Repeat the step 2 to uninstall all items under «Universal Serial Bus controllers».
Then, restart your computer and Windows Server will reinstall all USB controllers automatically.
Use the Keyboard
=============
First, please disconnect all USB devices. Then, go through the following steps:
1. Press «Ctrl + Esc» to open the Start Menu.
2. Type Device Manager in the Search bar and press «Enter». Click Continue if necessary.
3. In Device Manger, press Tab and use «Up» and «Down» to move the highlight to «Universal Serial Bus Controllers».
4. Press «Right» and expand it.
5. Press «Down» to move to the first item and press «Delete» to remove it.
6. Repeat the step 5 and uninstall all items under «Universal Serial Bus Controllers».
Then, restart your computer and Windows Server will reinstall all controllers automatically.
If the issue persists, please also contact the USB drive vendor for further assistance.
Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 15th, 2011 11:26pm