Wmic diskdrive get serialnumber ошибка - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

Windows 7 Enterprise Windows 7 Professional Windows 7 Ultimate Windows 7 Home Basic Windows 7 Home Premium 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 More…Less

Symptoms

Consider the following scenario. You connect a USB flash drive to a computer that is running Windows 7 or Windows Server 2008 R2. You try to run one of the following Windows Management Instrumentation Command-line (WMIC) tool commands to query the hard disk drives on the computer:

wmic diskdrive get *

wmic diskdrive get serialNumberIn this scenario, you receive an error message that resembles the following:

Invalid XML content

Cause

This issue occurs because the XML parser treats the control characters that are included in the serial number of some drives as invalid. Therefore, the XML parser cannot parse content that includes these control characters. This behavior causes valid results for other drives to be displayed incorrectly, together with the behavior that is mentioned in the «Symptoms» section.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or 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 the hotfix in this package, 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.

File information

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 notes

Important 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 1.17xxx	Windows 7 and Windows Server 2008 R2	SP1	GDR
6.1.760 1.21xxx	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
Wmic.exe	6.1.7601.17759	396,288	11-Jan-2012	05:34
Wmic.exe	6.1.7601.21895	396,288	11-Jan-2012	05:59

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	File version	File size	Date	Time
Wmic.exe	6.1.7601.17759	566,784	11-Jan-2012	06:35
Wmic.exe	6.1.7601.21895	566,784	11-Jan-2012	06:17

For all supported IA-64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time
Wmic.exe	6.1.7601.17759	1,074,688	11-Jan-2012	05:02
Wmic.exe	6.1.7601.21895	1,074,688	11-Jan-2012	05:15

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 the WMIC tool, visit the following Microsoft website:

How to use the WMIC toolFor 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

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_6c466840b6e63f63f610c157eb689892_31bf3856ad364e35_6.1.7601.17759_none_a7c0934712923ecf.manifest
File version	Not applicable
File size	712
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	X86_a876a9b062f41a0d4de85d1baa24c21b_31bf3856ad364e35_6.1.7601.21895_none_458609fa6ddfc3e2.manifest
File version	Not applicable
File size	712
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	X86_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.17759_none_a38b04d82b34f3eb.manifest
File version	Not applicable
File size	2,606
Date (UTC)	11-Jan-2012
Time (UTC)	06:18

File name	X86_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.21895_none_a3e560cb44769e1d.manifest
File version	Not applicable
File size	2,606
Date (UTC)	11-Jan-2012
Time (UTC)	07:05

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	Amd64_3d500f95fcbf849689fefcb7325c786f_31bf3856ad364e35_6.1.7601.21895_none_9650dc0e92149a9f.manifest
File version	Not applicable
File size	1,072
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_60d1a618a98c83d3b0ba72adf281e92c_31bf3856ad364e35_6.1.7601.21895_none_cd4f676a3ce6ab90.manifest
File version	Not applicable
File size	716
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_6c466840b6e63f63f610c157eb689892_31bf3856ad364e35_6.1.7601.17759_none_03df2ecacaefb005.manifest
File version	Not applicable
File size	714
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_a876a9b062f41a0d4de85d1baa24c21b_31bf3856ad364e35_6.1.7601.21895_none_a1a4a57e263d3518.manifest
File version	Not applicable
File size	714
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_bde56e055e65c9622ce1740fd94aef81_31bf3856ad364e35_6.1.7601.17759_none_1477ed41b5701bb4.manifest
File version	Not applicable
File size	1,072
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_c9c34784d98d026b6c1e90dee14ad8b6_31bf3856ad364e35_6.1.7601.17759_none_a008e51116613975.manifest
File version	Not applicable
File size	716
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Amd64_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.17759_none_ffa9a05be3926521.manifest
File version	Not applicable
File size	2,610
Date (UTC)	11-Jan-2012
Time (UTC)	07:40

File name	Amd64_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.21895_none_0003fc4efcd40f53.manifest
File version	Not applicable
File size	2,610
Date (UTC)	11-Jan-2012
Time (UTC)	07:31

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name	Ia64_4f90e151ff6a00729d20707864ceceb7_31bf3856ad364e35_6.1.7601.17759_none_421d1d510aabe246.manifest
File version	Not applicable
File size	1,070
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Ia64_d9ae40a789be5755cf49c836060dc0f1_31bf3856ad364e35_6.1.7601.21895_none_5a456f45388820ce.manifest
File version	Not applicable
File size	1,070
Date (UTC)	11-Jan-2012
Time (UTC)	14:06

File name	Ia64_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.17759_none_a38ca8ce2b32fce7.manifest
File version	Not applicable
File size	2,608
Date (UTC)	11-Jan-2012
Time (UTC)	06:56

File name	Ia64_microsoft-windows-w..ommand-line-utility_31bf3856ad364e35_6.1.7601.21895_none_a3e704c14474a719.manifest
File version	Not applicable
File size	2,608
Date (UTC)	11-Jan-2012
Time (UTC)	07:16

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Источник

I want to read the name and the serial number of my hard drives.

I stumbled upon wmic but I’m having troubles. I guess these two commands should do the trick, but I only get the message:

Invalid Xml-Content. //(Translated)

wmic path win32_physicalmedia get serialnumber

wmic DISKDRIVE GET SerialNumber

I tried the following as well:

wmic DISKDRIVE GET SerialNumber /FORMAT:list
wmic DISKDRIVE GET SerialNumber /FORMAT:xml.xsl
wmic DISKDRIVE GET SerialNumber > c:test.txt

Any ideas on what I’m doing wrong?

Solution:

Thanks JPBlanc, via the /? command I’ve found out that SerialNumber doesn’t even exist. I now use

WMIC /output:"c:hdds.txt" DISKDRIVE GET PNPDeviceID,Name /Format:CSV

which gives the correct result.

Источник

Remove From My Forums

Вопрос
i want to read the name and the serialnumber of my Hard-Drives. I stumbled upon wmic but i’m having troubles. these two commands should do the trick i guess, but only get the message: Invalid Xml-Content. //(Translated)

wmic path win32_physicalmedia get serialnumber

or

wmic DISKDRIVE GET SerialNumber

i tried the following aswell:

wmic DISKDRIVE GET SerialNumber /FORMAT:list wmic DISKDRIVE GET SerialNumber /FORMAT:xml.xsl wmic DISKDRIVE GET SerialNumber > c:test.txt

any ideas what i do wrong?

—————————————————————

Solution:

SerialNumber doesn’t even exist for DISKDRIVE, type WMIC DISKDRIVE GET /? to see available attributes.

WMIC /output:»c:hdds.txt» DISKDRIVE GET PNPDeviceID,Name /Format:CSV

this works fine for me.
- Изменено
  
  15 февраля 2012 г. 22:43

Ответы

well the problem is that

wmic DISKDRIVE GET Name

gives

\.PHYSICALDRIVE4
\.PHYSICALDRIVE2
\.PHYSICALDRIVE3

and thats what changes from time to time, these names get dynamically associated to the hdds. that by the way is my original problem. finding out which hdd has which name. would be wounderful if i could get the serialnumber and the name the same time.

heres my post in the truecrypt forum http://forums.truecrypt.org/viewtopic.php?p=100637#100637
- Помечено в качестве ответа
  Cloud_TS
  24 февраля 2012 г. 8:32

Источник

Я хочу прочитать имя и серийный номер моих жестких дисков.

Я наткнулся на wmic, но у меня проблемы. Я думаю, что эти две команды должны сделать свое дело, но я получаю только сообщение:

Invalid Xml-Content. //(Translated)

wmic path win32_physicalmedia get serialnumber

или же

wmic DISKDRIVE GET SerialNumber

Я попробовал следующее, а также:

wmic DISKDRIVE GET SerialNumber /FORMAT:list
wmic DISKDRIVE GET SerialNumber /FORMAT:xml.xsl
wmic DISKDRIVE GET SerialNumber > c:test.txt

Есть идеи, что я делаю не так?

Решение:

Спасибо JPBlanc, через /? Я обнаружил, что SerialNumber даже не существует. Я сейчас пользуюсь

WMIC /output:"c:hdds.txt" DISKDRIVE GET PNPDeviceID,Name /Format:CSV

который дает правильный результат.

2012-02-15 03:26

3
ответа

Решение

Вы просто делаете ошибку, используя командную строку WMIC, WMIC DISKDRIVE GET SerialNumber /Format /? дает вам ключевые слова:

CSV
HFORM
HTABLE
LIST
MOF
RAWXML
TABLE
VALUE
XML
htable-sortby
htable-sortby.xsl
texttablewsys
texttablewsys.xsl
wmiclimofformat
wmiclimofformat.xsl
wmiclitableformat
wmiclitableformat.xsl
wmiclitableformatnosys
wmiclitableformatnosys.xsl
wmiclivalueformat
wmiclivalueformat.xsl

ты можешь попробовать:

WMIC /output:"c:tempserial1.xml" DISKDRIVE GET SerialNumber /Format:RAWXML

Вы можете заменить RAWXML одним из других форматов.

2012-02-15 20:11

Я получал эту ошибку на Windows 7 x86 Pro (где запрос серийного номера должен быть возможен), когда был подключен внешний диск.

Вот как я это исправил:

Получить идентификатор каждого диска: wmic diskdrive get deviceid /format:list
Разберите вывод и получите первый идентификатор. В моем случае это было\.PHYSICALDRIVE0
Избегайте обратной косой черты, чтобы идентификатор \\.\PHYSICALDRIVE0
Получите серийный номер диска, используя его экранированный идентификатор:

wmic diskdrive where deviceid='\\.\PHYSICALDRIVE0' get serialnumber /format:list
Повторите шаги 2 — 4, пока не получите серийные номера всех дисков

Изменить: выше не работает на моей копии Windows XP x86 Pro.

Это делает:

wmic path win32_physicalmedia where tag='\\.\PHYSICALDRIVE0' get serialnumber /format:list

2014-05-26 13:34

Эта проблема возникает из-за того, что синтаксический анализатор XML рассматривает управляющие символы, включенные в серийный номер некоторых дисков, как недействительные.

2012-05-03 02:55

Источник

0 / 0 / 0

Регистрация: 25.09.2020

Сообщений: 4

25.09.2020, 12:28. Показов 4646. Ответов 8

Почему на моем служеьном компе с операционкой win7 команда wmic diskdrive get serialnumber выдает хэшированный номер?

0 / 0 / 0

Регистрация: 25.09.2020

Сообщений: 4

13.10.2020, 11:42

[ТС]

На других станциях вменяемо показывает серийник жесткого диска!

18042 / 7645 / 891

Регистрация: 25.12.2011

Сообщений: 11,426

Записей в блоге: 17

17.10.2020, 00:25

Сообщение было отмечено Dragokas как решение

Решение

Такая особенность в Win7.
Это ASCII символы в 16-ричном формате, и там еще байты попарно нужно обменивать при конвертации.

Вот здесь писал функцию:
Полезные BAT/CMD скрипты

0 / 0 / 0

Регистрация: 25.09.2020

Сообщений: 4

18.10.2020, 15:09

[ТС]

Спасибо Вам!

5407 / 3831 / 1214

Регистрация: 28.10.2013

Сообщений: 9,554

Записей в блоге: 1

18.10.2020, 17:47

Это выдает нормальные серийники (на win7 x64)

Код

wmic path Win32_PhysicalMedia Get SerialNumber

0 / 0 / 0

Регистрация: 25.09.2020

Сообщений: 4

18.10.2020, 18:32

[ТС]

Спасибо, вы лучшие!

0 / 0 / 0

Регистрация: 25.01.2022

Сообщений: 1

25.01.2022, 09:58

Реально такой серийник конвертировать в нормальный вид? ну хотя бы с помощью инженерного калькулятора…

FlasherX

5851 / 2563 / 1007

Регистрация: 06.06.2017

Сообщений: 8,750

25.01.2022, 15:28

Tramp78, реально:

Windows Batch file

@set @a=0/*&@echo off&setlocal enabledelayedexpansion
echo Model:  ^<Serial Number^>
for /f delims^= %%i in ('"wmic path Win32_DiskDrive WHERE Partitions=2 get Model,SerialNumber|findstr [0-9]"') do (
  set n=
  for %%x in (%%i) do set "n=!n! %%x" && set sn=%%x
  for /f %%# in ('cscript /e:jscript /nologo %0 !sn!') do call echo%%n: !sn!=%%:  %%#
)
pause>nul&exit
*/var h=WSH.arguments(0);r=''
for(var i=0;i<h.length;i+=4){r+='%'+h.substr(i+2,2)+'%'+h.substr(i,2)};WSH.echo(unescape(r).replace(/s/g,''))

.vbs:

Visual Basic

For Each D in GetObject("winmgmts:\.rootCIMV2").ExecQuery("SELECT Model,SerialNumber FROM Win32_DiskDrive WHERE Partitions=2")
   List = List & vbLf & SN(D.SerialNumber) & " (" & D.Model & ")"
Next
MsgBox Mid(List, 2), 262208
 
Function SN(Str)
   Dim S
   For i = 1 To Len(Str) Step 4
      Execute "S = S & ChrW(&H" & Mid(Str, i+2, 2) & ") & ChrW(&H" & Mid(Str, i, 2) & ")"
   Next
   SN = Trim(S)
End Function

18042 / 7645 / 891

Регистрация: 25.12.2011

Сообщений: 11,426

Записей в блоге: 17

25.01.2022, 20:51

Tramp78, выше выкладывал и принцип расчёта, и батник (если конечно уметь читать).

IT_Exp Эксперт 87844 / 49110 / 22898 Регистрация: 17.06.2006 Сообщений: 92,604	25.01.2022, 20:51
9

Источник

Symptoms

Cause

Resolution

Hotfix information

Prerequisites

Registry information

Restart requirement

Hotfix replacement information

File information

Windows 7 and Windows Server 2008 R2 file information notes

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

Status

More Information

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

Need more help?

Want more options?

Вопрос

Ответы

3 ответа

Решение

3
ответа