-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Surface Pro4
Ticket: 02680391/02680359
Hello i have an issue while trying to restore a Microsoft Surface pro 4 from a bootable USB key.
See the screeshot for the error message.
Secure boot is disabled.
https://www.dropbox.com/s/aaph57d9hmuws ... r.jpg?dl=0
Hello i have an issue while trying to restore a Microsoft Surface pro 4 from a bootable USB key.
See the screeshot for the error message.
Secure boot is disabled.
https://www.dropbox.com/s/aaph57d9hmuws ... r.jpg?dl=0
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Surface Pro4
Hello Tib.
Please check you BIOS settings and try to enable secure boot option (should be under boot options). Once enabled, save the settings, reboot your device and try to boot from recovery media again. Thanks!
Please check you BIOS settings and try to enable secure boot option (should be under boot options). Once enabled, save the settings, reboot your device and try to boot from recovery media again. Thanks!
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
Heya Dima, thank you for your answer,
I have already tried and the problem is the same with or without Secure boot.
Btw I forgot to say, i can boot up to bare metal restauration.
I can use all the otther tools, the error message is happening several seconds after clicking on Bare metal restauration.
I have already tried and the problem is the same with or without Secure boot.
Btw I forgot to say, i can boot up to bare metal restauration.
I can use all the otther tools, the error message is happening several seconds after clicking on Bare metal restauration.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
Hi Tib,
The problem I see in your screenshot seems something different.
When do you receive this error? booting up or trying to do the restore? If it is the restore, where are you getting your backup files from? Local USB device or a remote location?
The problem I see in your screenshot seems something different.
When do you receive this error? booting up or trying to do the restore? If it is the restore, where are you getting your backup files from? Local USB device or a remote location?
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
Soon after clicking on bare metal restauration.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
So the boot does work, but the moment you want to do BMR it starts to fail. Did you already went through steps off the wizard? (Trying to figure out where exactly it fails)
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
Nope and i have no idea how to do that.
Just in case a copy paste of the log.
Just in case a copy paste of the log.
Code: Select all
[15.03.2018 13:04:38] <01> Info ------- Veeam Endpoint Recovery Started -------
[15.03.2018 13:04:38] <01> Info Checking administrator rights as WindowsIdentity
[15.03.2018 13:04:40] <07> Info Creating \knowndll32: 0
[15.03.2018 13:04:40] <07> Info Creating KnownDllPath: 0
[15.03.2018 13:04:40] <11> Info Enable networking
[15.03.2018 13:04:40] <11> Info Generated hostname 'VeeamRe-ejyea0d'
[15.03.2018 13:04:40] <11> Info [WpeUtil] Invoking method WpeSetComputerName. Name: 'VeeamRe-ejyea0d'
[15.03.2018 13:04:40] Info < 8d8> Adding mount point [C:\] for volume \\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}.
[15.03.2018 13:04:40] <09> Info Getting list of volumes and disks on local machine (including removable disks).
[15.03.2018 13:04:40] Info < 8e0> Enumerating non shadow fixed volumes.
[15.03.2018 13:04:40] Info < 8e0> \\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}, label: 'Local Disk', file system: NTFS, DOS name: \Device\HarddiskVolume3
[15.03.2018 13:04:40] Info < 8e0> Mount points:
[15.03.2018 13:04:40] Info < 8e0> C:\
[15.03.2018 13:04:40] Info < 8e0> Extents:
[15.03.2018 13:04:40] Info < 8e0> Disk 0, offset407896064, length 253597057024
[15.03.2018 13:04:40] Info < 8d8> Trying to open hive: C:\Windows\System32\config\SOFTWARE
[15.03.2018 13:04:40] Info < 8e0> \\?\Volume{bd631667-2848-11e8-bc82-806e6f6e6963}, label: '', file system: FAT32, DOS name: \Device\HarddiskVolume5
[15.03.2018 13:04:40] Info < 8e0> Mount points:
[15.03.2018 13:04:40] Info < 8e0> D:\
[15.03.2018 13:04:40] Info < 8e0> Extents:
[15.03.2018 13:04:40] Info < 8e0> Disk 1, offset65536, length 3987668992
[15.03.2018 13:04:40] Info < 8e0> \\?\Volume{d6125e5e-145e-418e-8720-c212240d60f5}, label: 'Windows RE tools', file system: NTFS, DOS name: \Device\HarddiskVolume4
[15.03.2018 13:04:40] Info < 8e0> Mount points:
[15.03.2018 13:04:40] Info < 8e0> Extents:
[15.03.2018 13:04:40] Info < 8e0> Disk 0, offset254004953088, length 2055208960
[15.03.2018 13:04:40] Info < 8e0> \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}, label: 'Boot', file system: NTFS, DOS name: \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}
[15.03.2018 13:04:40] Info < 8e0> Mount points:
[15.03.2018 13:04:40] Info < 8e0> X:\
[15.03.2018 13:04:40] Info < 8e0> Extents:
[15.03.2018 13:04:40] Info < 8e0> Disk 4294967295, offset0, length 3161088
[15.03.2018 13:04:41] Info < 8d8> Trying to open hive: C:\Windows\System32\config\SOFTWARE. Ok.
[15.03.2018 13:04:41] Info < 8d8> Trying to open CurrentVersion key: OriginalSoftware\Microsoft\Windows NT\CurrentVersion
[15.03.2018 13:04:41] Info < 8d8> Trying to open CurrentVersion key: OriginalSoftware\Microsoft\Windows NT\CurrentVersion. Ok.
[15.03.2018 13:04:41] Info < 8d8> Trying to open hive: C:\Windows\System32\config\SAM
[15.03.2018 13:04:41] Info < 8d8> Trying to open hive: C:\Windows\System32\config\SAM. Ok.
[15.03.2018 13:04:41] Info < 8d8> Trying to find account key in: OriginalSAM\SAM\Domains\Account\Users\Names.
[15.03.2018 13:04:41] Info < 8d8> Skipping volume \\?\Volume{bd631667-2848-11e8-bc82-806e6f6e6963}: not a fixed drive (type: 2).
[15.03.2018 13:04:41] Info < 8d8> Adding mount point [X:\] for volume \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}.
[15.03.2018 13:04:41] Info < 8d8> Trying to open hive: X:\windows\System32\config\SOFTWARE
[15.03.2018 13:04:41] Info < 8d8> Trying to open hive: X:\windows\System32\config\SOFTWARE. Failed.
[15.03.2018 13:04:41] Warning < 8d8> Cannot find windows system in X:\
[15.03.2018 13:04:41] Warning < 8d8> Cannot open registry hive.
[15.03.2018 13:04:41] Warning < 8d8> Win32 error:The operation completed successfully.
Code: 0
[15.03.2018 13:04:41] Info < 8d8> . Ok.
[15.03.2018 13:06:41] Info < 8e0> Enumerating installed physical disks
[15.03.2018 13:06:41] Info < 8e0> Disk 0, capacity: 238.4GB, bus type: 17, read-only state: read-write, pack state: 1
[15.03.2018 13:06:41] Info < 8e0> Device: embedded, path: \\?\scsi#disk&ven_nvme&prod_thnsn5256gpu7_to#5&748d9a7&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:41] Info < 8e0> Layout: GPT, disk ID: {a678280b-cb65-4cc7-a4eb-e734c0f4abdf}
[15.03.2018 13:06:41] Info < 8e0> Partition 0, type ID {c12a7328-f81f-11d2-ba4b-00a0c93ec93b} (EFI system), ID {e835b506-3154-4809-bc2c-caa2f422124b}, offset 1048576, length 272629760
[15.03.2018 13:06:41] Info < 8e0> Partition 1, type ID {e3c9e316-0b5c-4db8-817d-f92df00215ae} (Microsoft reserved space), ID {feaa94e0-ee76-4716-b7e2-28f6f9d2d5ba}, offset 273678336, length 134217728
[15.03.2018 13:06:41] Info < 8e0> Partition 2, type ID {ebd0a0a2-b9e5-4433-87c0-68b6b72699c7} (basic data), ID {2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}, offset 407896064, length 253597057024
[15.03.2018 13:06:41] Info < 8e0> Partition 3, type ID {de94bba4-06d1-4d40-a16a-bfd50179d6ac} (Microsoft recovery), ID {d6125e5e-145e-418e-8720-c212240d60f5}, offset 254004953088, length 2055208960
[15.03.2018 13:06:41] Info < 8e0> Disk 1, capacity: 3.7GB, bus type: USB, read-only state: read-write, removable, pack state: 1
[15.03.2018 13:06:41] Info < 8e0> Device: external, path: \\?\usbstor#disk&ven_2.0&prod_usb_flash_drive&rev_1.00#6&1e11996a&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:41] Info < 8e0> Layout: MBR, disk signature: 7d47f8aa
[15.03.2018 13:06:41] Info < 8e0> Partition 0, type 0c (FAT32, LBA), offset 65536, length 3987668992
[15.03.2018 13:06:41] Info < 8e0> Enumerating installed physical disks. Ok.
[15.03.2018 13:06:41] Info < 8e0> Removing volume '\\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}' from result set : volumes resides on non-disk device.
[15.03.2018 13:06:41] Info < 8e0> Enumerating VDS volumes
[15.03.2018 13:06:41] Info < 8e0> Skipping VDS pack from volumes enumeration : pack is offline.
[15.03.2018 13:06:41] Info < 8e0> Volume name: \\?\GLOBALROOT\Device\HarddiskVolume3, type: VDS_VT_SIMPLE, is online
[15.03.2018 13:06:41] Info < 8e0> GUID path names:
[15.03.2018 13:06:41] Info < 8e0> \\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}\
[15.03.2018 13:06:41] Info < 8e0> Volume name: \\?\GLOBALROOT\Device\HarddiskVolume5, type: VDS_VT_SIMPLE, is online
[15.03.2018 13:06:41] Info < 8e0> GUID path names:
[15.03.2018 13:06:41] Info < 8e0> \\?\Volume{bd631667-2848-11e8-bc82-806e6f6e6963}\
[15.03.2018 13:06:41] Info < 8e0> Enumerating VDS volumes. Ok.
[15.03.2018 13:06:41] Info < 8e0> Boot volume is '{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}', disk number: '-1'.
[15.03.2018 13:06:41] Error < 8e0> Unable to retrieve system volume device name.
[15.03.2018 13:06:41] Warning < 8e0> Cannot retrieve a registry value. Value name: [SystemPartition].
[15.03.2018 13:06:41] Warning < 8e0> Registry query value fail.
[15.03.2018 13:06:41] Warning < 8e0> Win32 error:The operation completed successfully.
Code: 0
[15.03.2018 13:06:41] Info < 8e0> system volume device: ''.
[15.03.2018 13:06:41] Info < 8e0> Volume '\\?\Volume{bd631667-2848-11e8-bc82-806e6f6e6963}' is an MBR boot volume, but it doesn't placed on windows system disk, windows disk id '-1'. System volume dev. name: '', volume dev. name: '\Device\HarddiskVolume5'.
[15.03.2018 13:06:41] Info < 8e0> Volume '\\?\Volume{d6125e5e-145e-418e-8720-c212240d60f5}' is an GPT recovery volume.
[15.03.2018 13:06:41] <09> Info Layout: '<ShadowVolumesLayout><ShadowVolumes/><LiveVolumes><LiveVolume Id="{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}" Name="\\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}" Label="Local Disk" FilesystemType="NTFS" Capacity="253597057024" UsedSize="71757070336" Roles="0" VdsType="VDS_VT_SIMPLE" VdsOfflineStatus="false"><MountPoints><MountPoint Path="C:\"/></MountPoints><Extents><Extent DiskNumber="0" StartingOffset="407896064" ExtentLength="253597057024"/></Extents></LiveVolume><LiveVolume Id="{bd631667-2848-11e8-bc82-806e6f6e6963}" Name="\\?\Volume{bd631667-2848-11e8-bc82-806e6f6e6963}" Label="" FilesystemType="FAT32" Capacity="3987668992" UsedSize="1429254144" Roles="0" VdsType="VDS_VT_SIMPLE" VdsOfflineStatus="false"><MountPoints><MountPoint Path="D:\"/></MountPoints><Extents><Extent DiskNumber="1" StartingOffset="65536" ExtentLength="3987668992"/></Extents></LiveVolume><LiveVolume Id="{d6125e5e-145e-418e-8720-c212240d60f5}" Name="\\?\Volume{d6125e5e-145e-418e-8720-c212240d60f5}" Label="Windows RE tools" FilesystemType="NTFS" Capacity="2055208960" UsedSize="956989440" Roles="1" VdsType="VDS_VT_SIMPLE" VdsOfflineStatus="false"><MountPoints/><Extents><Extent DiskNumber="0" StartingOffset="254004953088" ExtentLength="2055208960"/></Extents></LiveVolume></LiveVolumes><Disks><Disk DiskNumber="0" BusType="17" Capacity="256060514304" IsReadOnly="false" ReadOnlyState="2" IsVirtualDisk="false" IsRemovable="false" LogicalSectorSize="512" FriendlyName="THNSN5256GPU7 TOSHIBA" PackStateFlags="1"><DriveLayout PartitionStyle="GPT" DiskId="{a678280b-cb65-4cc7-a4eb-e734c0f4abdf}" StartingUsableOffset="17408" UsableLength="256060480000" MaxPartitionCount="128"><Partitions><Partition PartitionNumber="1" StartingOffset="1048576" PartitionLength="272629760" PartitionStyle="GPT" PartitionType="{c12a7328-f81f-11d2-ba4b-00a0c93ec93b}" PartitionId="{e835b506-3154-4809-bc2c-caa2f422124b}" Attributes="9223372036854775808" Name="EFI system partition"/><Partition PartitionNumber="2" StartingOffset="273678336" PartitionLength="134217728" PartitionStyle="GPT" PartitionType="{e3c9e316-0b5c-4db8-817d-f92df00215ae}" PartitionId="{feaa94e0-ee76-4716-b7e2-28f6f9d2d5ba}" Attributes="9223372036854775808" Name="Microsoft reserved partition"/><Partition PartitionNumber="3" StartingOffset="407896064" PartitionLength="253597057024" PartitionStyle="GPT" PartitionType="{ebd0a0a2-b9e5-4433-87c0-68b6b72699c7}" PartitionId="{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}" Attributes="0" Name="Basic data partition"/><Partition PartitionNumber="4" StartingOffset="254004953088" PartitionLength="2055208960" PartitionStyle="GPT" PartitionType="{de94bba4-06d1-4d40-a16a-bfd50179d6ac}" PartitionId="{d6125e5e-145e-418e-8720-c212240d60f5}" Attributes="9223372036854775809" Name="Basic data partition"/></Partitions></DriveLayout><DevSetupInfo DevPath="\\?\scsi#disk&ven_nvme&prod_thnsn5256gpu7_to#5&748d9a7&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" IsExternalDisk="false"/></Disk><Disk DiskNumber="1" BusType="USB" Capacity="3987734528" IsReadOnly="false" ReadOnlyState="2" IsVirtualDisk="false" IsRemovable="true" LogicalSectorSize="512" FriendlyName="2.0 USB Flash Drive USB Device" PackStateFlags="1"><DriveLayout PartitionStyle="MBR" Signature="2101868714"><Partitions><Partition PartitionNumber="1" StartingOffset="65536" PartitionLength="3987668992" PartitionStyle="MBR" PartitionType="12" BootIndicator="true" RecognizedPartition="true" HiddenSectors="128"/><Partition PartitionNumber="0" StartingOffset="0" PartitionLength="0" PartitionStyle="MBR" PartitionType="0" BootIndicator="false" RecognizedPartition="true" HiddenSectors="0"/><Partition PartitionNumber="0" StartingOffset="0" PartitionLength="0" PartitionStyle="MBR" PartitionType="0" BootIndicator="false" RecognizedPartition="true" HiddenSectors="0"/><Partition PartitionNumber="0" StartingOffset="0" PartitionLength="0" PartitionStyle="MBR" PartitionType="0" BootIndicator="false" RecognizedPartition="true" HiddenSectors="0"/></Partitions></DriveLayout><DevSetupInfo DevPath="\\?\usbstor#disk&ven_2.0&prod_usb_flash_drive&rev_1.00#6&1e11996a&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" IsExternalDisk="true"/></Disk></Disks></ShadowVolumesLayout>
[15.03.2018 13:06:41] <09> Info '
[15.03.2018 13:06:42] <09> Info Checking disk bus type 17. ProcessSharedDisks = False
[15.03.2018 13:06:42] <09> Info Checking disk bus type USB. ProcessSharedDisks = False
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Using win path 'C:\Windows; Windows 10 Pro Version: 6.3; Administrateur'
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Using registry path 'C:\windows\system32\config\system'
[15.03.2018 13:06:42] <08> Info Do not copy registry hive before load.
[15.03.2018 13:06:42] <08> Info [Registry] Checking registry file header, filePath = 'C:\windows\system32\config\system'
[15.03.2018 13:06:42] <08> Info [Registry] SeqNumber1 is 13550, SeqNumber2 is 13549
[15.03.2018 13:06:42] <08> Warning [Registry] registry file update will be performed
[15.03.2018 13:06:42] <08> Info [Registry] Registry file was updated
[15.03.2018 13:06:42] <08> Info [Registry] Loading registry hive 'system4a5439ea083442a7b2bc297adba13bea' from file 'C:\windows\system32\config\system'
[15.03.2018 13:06:42] <08> Info Enumerating values from 'MountedDevices'
[15.03.2018 13:06:42] <08> Info \DosDevices\C: : DMIO ID 2a48ef84-54f6-40c2-ab34-fbabd7fa25b6
[15.03.2018 13:06:42] <08> Info \DosDevices\D: : _??_USBSTOR#Disk&Ven_2.0&Prod_USB_Flash_Drive&Rev_1.00#6&1e11996a&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:42] <08> Info \DosDevices\E: : 5C-00-3F-00-3F-00-5C-00-53-00-43-00-53-00-49-00-23-00-43-00-64-00-52-00-6F-00-6D-00-26-00-56-00-65-00-6E-00-5F-00-4D-00-73-00-66-00-74-00-26-00-50-00-72-00-6F-00-64-00-5F-00-56-00-69-00-72-00-74-00-75-00-61-00-6C-00-5F-00-44-00-56-00-44-00-2D-00-52-00-4F-00-4D-00-23-00-32-00-26-00-31-00-66-00-34-00-61-00-64-00-66-00-66-00-65-00-26-00-30-00-26-00-30-00-30-00-30-00-30-00-30-00-31-00-23-00-7B-00-35-00-33-00-66-00-35-00-36-00-33-00-30-00-64-00-2D-00-62-00-36-00-62-00-66-00-2D-00-31-00-31-00-64-00-30-00-2D-00-39-00-34-00-66-00-32-00-2D-00-30-00-30-00-61-00-30-00-63-00-39-00-31-00-65-00-66-00-62-00-38-00-62-00-7D-00
[15.03.2018 13:06:42] <08> Info \??\Volume{092cc211-cb75-11e6-b58c-bc83851a3dfb} : _??_USBSTOR#Disk&Ven_Generic&Prod_Flash_Disk&Rev_8.07#6D52D3C4&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:42] <08> Info \??\Volume{e45d231c-2790-11e8-b58f-bc83851a3dfb} : 5C-00-3F-00-3F-00-5C-00-53-00-43-00-53-00-49-00-23-00-43-00-64-00-52-00-6F-00-6D-00-26-00-56-00-65-00-6E-00-5F-00-4D-00-73-00-66-00-74-00-26-00-50-00-72-00-6F-00-64-00-5F-00-56-00-69-00-72-00-74-00-75-00-61-00-6C-00-5F-00-44-00-56-00-44-00-2D-00-52-00-4F-00-4D-00-23-00-32-00-26-00-31-00-66-00-34-00-61-00-64-00-66-00-66-00-65-00-26-00-30-00-26-00-30-00-30-00-30-00-30-00-30-00-31-00-23-00-7B-00-35-00-33-00-66-00-35-00-36-00-33-00-30-00-64-00-2D-00-62-00-36-00-62-00-66-00-2D-00-31-00-31-00-64-00-30-00-2D-00-39-00-34-00-66-00-32-00-2D-00-30-00-30-00-61-00-30-00-63-00-39-00-31-00-65-00-66-00-62-00-38-00-62-00-7D-00
[15.03.2018 13:06:42] <08> Info \??\Volume{e8951990-27a6-11e8-b591-bc83851a3dfb} : _??_USBSTOR#Disk&Ven_2.0&Prod_USB_Flash_Drive&Rev_1.00#6&1e11996a&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:42] <08> Info \??\Volume{66f3ba9c-27ab-11e8-b592-bc83851a3dfb} : _??_USBSTOR#Disk&Ven_2.0&Prod_USB_Flash_Drive&Rev_1.00#7&106e859&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
[15.03.2018 13:06:42] <08> Info [Registry] Unloading registry hive 'system4a5439ea083442a7b2bc297adba13bea'
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Remapping device 'C:'
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Device '2a48ef84-54f6-40c2-ab34-fbabd7fa25b6'
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Volume found: \\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}
[15.03.2018 13:06:42] <08> Error Failed to delete volume mount point C:'
[15.03.2018 13:06:42] <08> Error More data is available (System.ComponentModel.Win32Exception)
[15.03.2018 13:06:42] <08> Error at Veeam.Backup.Common.Disk.NativeAPI.DeleteVolumeMountPoint(String mountPoint)
[15.03.2018 13:06:42] <08> Error at Veeam.EndPoint.Core.CDriveLetterMapper.SafeDeleteVolumeMountPoint(String mountPoint)
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Set mount point 'C:' for volume '\\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}'
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Set mount point 'E:' for volume '\\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}\'
[15.03.2018 13:06:42] <08> Error Failed to set volume '\\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}\' mount point 'E:'
[15.03.2018 13:06:42] <08> Error Cannot create a file when that file already exists (System.ComponentModel.Win32Exception)
[15.03.2018 13:06:42] <08> Error at Veeam.Backup.Common.Disk.NativeAPI.SetVolumeMountPoint(String volumeName, String mountPoint)
[15.03.2018 13:06:42] <08> Error at Veeam.EndPoint.Core.CDriveLetterMapper.SafeSetVolumeMountPoint(String volumeName, String mountPoint)
[15.03.2018 13:06:42] <08> Info [DriveLetterMapper] Set mount point failed. Try to set free drive letter
[15.03.2018 13:06:42] <08> Error Failed to set volume '\\?\Volume{2a48ef84-54f6-40c2-ab34-fbabd7fa25b6}\' mount point 'E:'
[15.03.2018 13:06:42] <08> Error Cannot create a file when that file already exists (System.ComponentModel.Win32Exception)
[15.03.2018 13:06:42] <08> Error at Veeam.Backup.Common.Disk.NativeAPI.SetVolumeMountPoint(String volumeName, String mountPoint)
[15.03.2018 13:06:42] <08> Error at Veeam.EndPoint.Core.CDriveLetterMapper.SafeSetVolumeMountPoint(String volumeName, String mountPoint)
[15.03.2018 13:09:40] <11> Info [WpeUtil] Invoking method InitializeNetworkW commandline ''
[15.03.2018 13:10:33] <11> Info [WpeUtil] Invoking method DisableFirewallW commandline ''
[15.03.2018 13:10:33] <11> Error Failed to start dnscache
[15.03.2018 13:10:33] <11> Error Cannot start service Dnscache on computer '.'. (System.InvalidOperationException)
[15.03.2018 13:10:33] <11> Error at System.ServiceProcess.ServiceController.Start(String[] args)
[15.03.2018 13:10:33] <11> Error at Veeam.EndPoint.CApplianceNetworkManager.StartDnsCacheSafe()
[15.03.2018 13:10:33] <11> Error An instance of the service is already running (System.ComponentModel.Win32Exception)
[15.03.2018 13:10:33] <11> Info [CNetworkConfigurator] Updating network interfaces from saved settings
[15.03.2018 13:10:33] <11> Info [CNetworkConfigurator] Loading saved network settings
[15.03.2018 13:10:33] <11> Info [Netsh] Running netsh with command line 'interface ip set address name="Local Area Connection* 2" dhcp'
[15.03.2018 13:10:34] <11> Error Failed to set network Local Area Connection* 2 ip settings
[15.03.2018 13:10:34] <11> Error The following helper DLL cannot be loaded: WLANCFG.DLL.DHCP is already enabled on this interface. (System.Exception)
[15.03.2018 13:10:34] <11> Error at Veeam.EndPoint.Core.Netsh.RunNetsh(String arguments)
[15.03.2018 13:10:34] <11> Error at Veeam.EndPoint.Core.CNetworkConfigurator.SetNetworkSettings(String ifaceName, CNetwrokInterfaceInfo info)
[15.03.2018 13:10:34] <11> Info [Netsh] Running netsh with command line 'interface ip set dns "Local Area Connection* 2" dhcp'
[15.03.2018 13:10:34] <11> Info [Netsh] Running netsh with command line 'interface ip set address name="WiFi" dhcp'
[15.03.2018 13:10:34] <11> Error Failed to set network WiFi ip settings
[15.03.2018 13:10:34] <11> Error The following helper DLL cannot be loaded: WLANCFG.DLL.DHCP is already enabled on this interface. (System.Exception)
[15.03.2018 13:10:34] <11> Error at Veeam.EndPoint.Core.Netsh.RunNetsh(String arguments)
[15.03.2018 13:10:34] <11> Error at Veeam.EndPoint.Core.CNetworkConfigurator.SetNetworkSettings(String ifaceName, CNetwrokInterfaceInfo info)
[15.03.2018 13:10:34] <11> Info [Netsh] Running netsh with command line 'interface ip set dns "WiFi" dhcp'
[15.03.2018 13:10:34] <11> Info [CNetworkConfigurator] Connecting to wireless network
****removing all the wifi*****
[15.03.2018 13:10:37] <07> Info Starting VDS service
[15.03.2018 13:12:38] <07> Info Creating \knowndll32: C0000035
[15.03.2018 13:12:38] <07> Info Opening \knowndll32: 0
[15.03.2018 13:12:38] <07> Info Creating KnownDllPath: C0000035
[15.03.2018 13:12:38] <07> Info [CEpApplianceTransportService] Starting transport service
[15.03.2018 13:12:38] <07> Info [RpcTransport] Starting on port 3128
[15.03.2018 13:12:38] <07> Info [RpcTransport] Started on port 3128
[15.03.2018 13:12:39] <01> Info [CWifiServiceStarter] Starting wifi configuration services
[15.03.2018 13:12:39] <01> Info [wmi(localhost)] Opening WMI namespace 'root\cimv2' on server 'localhost'. Account: '<current>'.
[15.03.2018 13:13:39] <01> Error Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED)) (System.Runtime.InteropServices.COMException)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.ThrowNotConnectedExc(Exception connectExc)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.Reconnect()
[15.03.2018 13:13:39] <01> Error Failed to get os version
[15.03.2018 13:13:39] <01> Error Server 'localhost' does not exist or access denied.
[15.03.2018 13:13:39] <01> Error Check firewall settings. (System.InvalidOperationException)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.Reconnect()
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.GetVersion(String serverName, CCredentials creds)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.GetVersion()
[15.03.2018 13:13:39] <01> Error Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED)) (System.Runtime.InteropServices.COMException)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.ThrowNotConnectedExc(Exception connectExc)
[15.03.2018 13:13:39] <01> Error at Veeam.Backup.Common.CWMIInvoker.Reconnect()
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Installing net component 'MS_NDISUIO'
[15.03.2018 13:13:39] <01> Info Creating netcfg instance
[15.03.2018 13:13:39] <01> Info Creating lock instance
[15.03.2018 13:13:39] <01> Info Acquiring lock for write
[15.03.2018 13:13:39] <01> Info Initializing net cfg
[15.03.2018 13:13:39] <01> Info Quering component setup instance
[15.03.2018 13:13:39] <01> Info Install component
[15.03.2018 13:13:39] <01> Info Apply changes
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Net component installed successfully
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Installing net component 'MS_NATIVEWIFIP'
[15.03.2018 13:13:39] <01> Info Creating netcfg instance
[15.03.2018 13:13:39] <01> Info Creating lock instance
[15.03.2018 13:13:39] <01> Info Acquiring lock for write
[15.03.2018 13:13:39] <01> Info Initializing net cfg
[15.03.2018 13:13:39] <01> Info Quering component setup instance
[15.03.2018 13:13:39] <01> Info Install component
[15.03.2018 13:13:39] <01> Info Apply changes
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Net component installed successfully
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Installing net component 'MS_VWIFI'
[15.03.2018 13:13:39] <01> Info Creating netcfg instance
[15.03.2018 13:13:39] <01> Info Creating lock instance
[15.03.2018 13:13:39] <01> Info Acquiring lock for write
[15.03.2018 13:13:39] <01> Info Initializing net cfg
[15.03.2018 13:13:39] <01> Info Quering component setup instance
[15.03.2018 13:13:39] <01> Info Install component
[15.03.2018 13:13:39] <01> Info Apply changes
[15.03.2018 13:13:39] <01> Info [CNetComponentInstaller] Net component installed successfully
[15.03.2018 13:13:39] <01> Info [CWifiServiceStarter] Starting service 'wlansvc'
[15.03.2018 13:13:39] <01> Info [CWifiServiceStarter] Starting service 'dot3svc'
[15.03.2018 13:13:40] <01> Info [CWifiServiceStarter] Starting service 'lanmanserver'
[15.03.2018 13:14:13] <01> Info [CWifiServiceStarter] Starting service 'netman'
[15.03.2018 13:14:14] <01> Info [CWifiServiceStarter] Wifi configuration services started
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
Our support engineers will be able to see much better where the issue is then I can, but it looks to me that you are not getting an IP on the wifi and (am I correct in assuming so?) you will need that to connect to the location that holds the backup.
Can you take that surface, boot again on the thumbdrive and then go to the tools and run command prompt to see if you get an IP? (Ipconfig)
Can you take that surface, boot again on the thumbdrive and then go to the tools and run command prompt to see if you get an IP? (Ipconfig)
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
Thanks Mike, i am trying now, the boot up to the BRM is very slow, something like 7 minutes on this computer.
Make it 10 still booting, well "recovery environement is installing"
Is it mapping all the wifi around?
IPCONFIG completed and everything is ok, i have an ip
Clicking on BRM but then again i have the same error message (see the screenshot in my seconbd message)
Fyi i am downloading the lastest release of VRM from Veeam FTP
Make it 10 still booting, well "recovery environement is installing"
Is it mapping all the wifi around?
IPCONFIG completed and everything is ok, i have an ip
Clicking on BRM but then again i have the same error message (see the screenshot in my seconbd message)
Fyi i am downloading the lastest release of VRM from Veeam FTP
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
Most likely the reason for the slow boot up is the thumb drive. I have noticed that cheaper models (or older ones) go on USB 2 when you do this for a surface pro which limits the speed.
If WiFi is OK, that means you should be able to connect to the storage that holds the backup (at least if it is over the network, you still need to tell me where the location of the backup is )
In that case, I would continue to work with support so they can see what is blocking this. I can see it is a remote procedure call that fails but not what exactly is failing
If WiFi is OK, that means you should be able to connect to the storage that holds the backup (at least if it is over the network, you still need to tell me where the location of the backup is )
In that case, I would continue to work with support so they can see what is blocking this. I can see it is a remote procedure call that fails but not what exactly is failing
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
This is working perfectly well with VRM!
And this is much faster!
Restauring right now..
I have another issue but this is related to the computer, nothing serious anyway.(different disk partitions, that replaced surface pro4 must be sightly different from the one before,
Veeam was a litle lost with all the partitiions, i am reastauring the C: only)
Thank you very much everyone!
Best regards.
Thibault
And this is much faster!
Restauring right now..
I have another issue but this is related to the computer, nothing serious anyway.(different disk partitions, that replaced surface pro4 must be sightly different from the one before,
Veeam was a litle lost with all the partitiions, i am reastauring the C: only)
Thank you very much everyone!
Best regards.
Thibault
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
Good news Thibault!
About the partitions. That is indeed possible but we have an advanced restore capability that allows you to map the partitions. What you can do however (now that you are restoring) is simply recover the other partition afterwards. As long if it is not the C-volume (or volume used for the OS) then you can do a volume recovery afterwards also.
PS: I just noticed you are saying VRM? What solution are you exactly using?
About the partitions. That is indeed possible but we have an advanced restore capability that allows you to map the partitions. What you can do however (now that you are restoring) is simply recover the other partition afterwards. As long if it is not the C-volume (or volume used for the OS) then you can do a volume recovery afterwards also.
PS: I just noticed you are saying VRM? What solution are you exactly using?
-
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: Mar 16, 2018 10:51 am
- Contact:
Re: Surface Pro4
Veeam Recovery Media
One of the partition was sightly different +300Ko
One of the partition was sightly different +300Ko
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Surface Pro4
Ah. Understood. For us it is all part of VAW (Veeam agent for Windows)
But all good. And yes, for that slightly different partition, you could have used the advanced part in the wizard which would help you in mapping it.
But all good. And yes, for that slightly different partition, you could have used the advanced part in the wizard which would help you in mapping it.
Who is online
Users browsing this forum: No registered users and 12 guests