DiskPartitioning Failure

Moderator: jknoth

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

DiskPartitioning Failure

Beitrag von ctearney » 01. Feb 2019, 21:05

On certain models we are seeing that the DiskPartitioning PreOS package is not able to completed. I have tried with version 3.8 & 3.9 and am seeing the same results but different error messages. I thought maybe the update WinPE package and preOS builds would resolve but they did not.

Since it is only occurring on select models like the Lenovo T560 I can only assume that is a device variance or setting that is causing the problem.

3.9
01.02.2019 13:14:19 COSERV TEST-T560 coserv\sa_m42svc_clms DiskPartitioning 3.9 3.9 0 Install Failure Remove-PartitionAccessPath : Cannot remove the drive letter of a boot or paging file partition.


01.02.2019 13:53:11 [PEAgent] [Windows] PreOS Package execution failure. Rebooting client in 300 seconds.
01.02.2019 13:53:10 [PEAgent] [Windows] Operation not supported on a critical disk.
Activity ID: {3cce19a3-fe47-4cc9-a6cc-37da74b8ccd1}
01.02.2019 13:53:04 [PEAgent] [Windows] Start to execute Matrix42\OsPackages\DiskPartitioning\3.8 package.

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 04. Feb 2019, 21:24

Figured out that a hidden partition was generated on the devices which the DiskPartioning package was having issue managing. Using DISKPART from a WinPE boot drive to remove all partitions allowed for the image process to go thru without issue. This is just odd that this started to occur as I had not had issues before with these models. Oh, well. all fixed.

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 14. Feb 2019, 21:23

Well, the issue has returned and its not as simple as clearing a hidden partition this time. I included the log files below from UAF agent but the short of it is that the partition disk PreOS package is attempting to clear the drive letter on the primary partition with the OS after the Windows Installation portion of the process has already completed. "Remove-PartitionAccessPath"

As before this is not happening on all devices, I am getting this problem on a Lenovo T470 but using the same the image configuration group turn around and image a Dell 5490 and a Lenovo x260. On the T470 I have tried updating the bios, resetting the bios to factory default, replaced the M2 drive with a brand new one, changed bios to legacy from UEFI. Nothing seems to impact this problem.

I am at a loss of what to try next. Any suggestions?

019-02-14 09:13:17.366 [Information] [Process.OutputReadNotifyUser] Read the following variable values for Disk 0 from the Computer.ini:
2019-02-14 09:13:17.369 [Information] [Process.OutputReadNotifyUser] SizeSystemPartition: 100
2019-02-14 09:13:17.369 [Information] [Process.OutputReadNotifyUser] SizeDataPartition: 0
2019-02-14 09:13:17.370 [Information] [Process.OutputReadNotifyUser] InterpretSizeInputAsProcentage: 1
2019-02-14 09:13:17.371 [Information] [Process.OutputReadNotifyUser] MinimumSystemPartitionSize: 0
2019-02-14 09:13:17.372 [Information] [Process.OutputReadNotifyUser] PreferFastDisk: 0
2019-02-14 09:13:17.372 [Information] [Process.OutputReadNotifyUser] ClearAllDisks: 0
2019-02-14 09:13:17.373 [Information] [Process.OutputReadNotifyUser] Information before DiskPartitioning ...
2019-02-14 09:13:17.374 [Information] [Process.OutputReadNotifyUser] Current hard disk information:
2019-02-14 09:13:17.375 [Information] [Process.OutputReadNotifyUser] ==============================
2019-02-14 09:13:20.605 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.606 [Information] [Process.OutputReadNotifyUser] Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
2019-02-14 09:13:20.606 [Information] [Process.OutputReadNotifyUser] Style
2019-02-14 09:13:20.606 [Information] [Process.OutputReadNotifyUser] ------ ------------- ------------- ------------ ----------------- ---------- ----------
2019-02-14 09:13:20.672 [Information] [Process.OutputReadNotifyUser] 0 SAMSUNG MZ... 0025_38B7_71BA_6005. Healthy Online 476.94 GB GPT
2019-02-14 09:13:20.672 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.672 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.673 [Information] [Process.OutputReadNotifyUser] Current partition information:
2019-02-14 09:13:20.673 [Information] [Process.OutputReadNotifyUser] ==============================
2019-02-14 09:13:20.705 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.706 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.706 [Information] [Process.OutputReadNotifyUser] DiskPath: \\?\scsi#disk&ven_nvme&prod_samsung_mzvlw512#5&36c9cf4f&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
2019-02-14 09:13:20.706 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.706 [Information] [Process.OutputReadNotifyUser] PartitionNumber DriveLetter Offset Size Type
2019-02-14 09:13:20.706 [Information] [Process.OutputReadNotifyUser] --------------- ----------- ------ ---- ----
2019-02-14 09:13:20.723 [Information] [Process.OutputReadNotifyUser] 1 1048576 300 MB Recovery
2019-02-14 09:13:20.724 [Information] [Process.OutputReadNotifyUser] 2 315621376 100 MB System
2019-02-14 09:13:20.724 [Information] [Process.OutputReadNotifyUser] 3 420478976 128 MB Reserved
2019-02-14 09:13:20.725 [Information] [Process.OutputReadNotifyUser] 4 C 554696704 476.42 GB Basic
2019-02-14 09:13:20.725 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.725 [Information] [Process.OutputReadNotifyUser]
2019-02-14 09:13:20.742 [Information] [Process.OutputReadNotifyUser] Start to remove drive letter assignments.
2019-02-14 09:13:20.787 [Information] [Process.OutputReadNotifyUser] Removing drive letter C from disk 0 and partition 4
2019-02-14 09:13:21.054 [Error] [Process.ErrorReadNotifyUser] Remove-PartitionAccessPath : Cannot remove the drive letter of a boot or paging file partition.
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] Activity ID: {de46d2a1-e52a-43de-9769-ab984e5fe808}
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] At \\EMPIRUM.coserv.com\Configurator$\Packages\Matrix42\OsPackages\DiskPartitioning\3.8\install\install.ps1:374 char:9
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] + Remove-PartitionAccessPath -DiskNumber $partition.DiskNumber ...
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] + CategoryInfo : InvalidOperation: (StorageWMI:ROOT/Microsoft/.../MSFT_Partition) [Remove-PartitionAccess
2019-02-14 09:13:21.180 [Error] [Process.ErrorReadNotifyUser] Path], CimException
2019-02-14 09:13:21.181 [Error] [Process.ErrorReadNotifyUser] + FullyQualifiedErrorId : StorageWMI 42006,Remove-PartitionAccessPath
2019-02-14 09:13:21.181 [Error] [Process.ErrorReadNotifyUser]
2019-02-14 09:13:21.188 [Information] [Process.OutputReadNotifyUser] Clearing disk 0 ...
2019-02-14 09:13:21.387 [Information] [PeAgentService.SendPxeLogMessage] SendPxeLogMessage called with log message: Operation not supported on a critical disk.
Activity ID: {1e1d3574-6681-4863-b870-518e14bc2457}

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 15. Feb 2019, 15:49

Hi ctearney,

You could try the following Feature for that device:

Add the Variable 'ClearAllDisks' to DiskPartitioning variable definition as number variable and set it to 1.
That will clear all available disks before trying to remove assigned drive letters.

That might help you.
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 15. Feb 2019, 21:12

Thank you for the suggestion. I added that variable and gave it another try, unfortunately that did not fix it. I am going to look at the bios again to see if there is anything else I can try.

15.02.2019 14:05:24 [PEAgent] [Windows] PE Agent error, rebooting client in 300 seconds.
15.02.2019 14:05:22 [PEAgent] [Windows] Operation not supported on a critical disk. Activity ID: {4704ed0b-191d-46f5-9a845612621325}
15.02.2019 14:04:14 [PEAgent] [Windows] Start to execute Matrix42\OsPackages\DiskPartitioning\3.9 package.
15.02.2019 13:39:40 [PEAgent] [WinPE] PE Agent error, rebooting client in 300 seconds.
15.02.2019 13:39:38 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\WindowsInstallation\4.7 package.
15.02.2019 13:33:26 [PEAgent] [WinPE] Using image file \\EMPIRUM.coserv.com\EmpInst$\Sys\win10\x64\pro\0_bc9fe15c-9045-46f4-b785-a6d69eb5c225\en-US\VISTADVD\install.wim.
15.02.2019 13:33:22 [PEAgent] [WinPE] Using default unattend.xml template.
15.02.2019 13:33:14 [PEAgent] [WinPE] Start to execute Matrix42\OsPackages\WindowsInstallation\4.7 package.
15.02.2019 13:33:10 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\DriverIntegration\2.6 package.
15.02.2019 13:33:10 [PEAgent] [WinPE] Using the drivers: '20HD005GUS-T470.zip' for vendor 'LENOVO' and model '20HD005GUS'.
15.02.2019 13:32:28 [PEAgent] [WinPE] Start to execute Matrix42\OsPackages\DriverIntegration\2.6 package.
15.02.2019 13:32:24 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\DiskPartitioning\3.9 package.
15.02.2019 13:32:24 [PEAgent] [WinPE] Hard disk formating/partitioning successful.
15.02.2019 13:31:40 [PEAgent] [WinPE] Start to execute Matrix42\OsPackages\DiskPartitioning\3.9 package.

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 15. Feb 2019, 22:38

Hey ctearney,

from you last Log here, I can see, that you're executing DiskPartitioning package under Windows and not under WinPE - that is wrong and will not work!

If that was not intended, so please check the order of the PreOS Packages within Software Depot in EMC. Check out the How To PDF for reference.
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 15. Feb 2019, 22:41

And I see also in your first post, that you run DiskPartitionkng at Windows time and not at WinPE time. Really check the order of PreOs Packages in Software Depot.
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 15. Feb 2019, 22:54

The order is correct (I checked it a few times :D ). I do not know why but on the T470 the diskpart package runs twice, once at the beginning which is successful and then again after the WindowsInstall package completes. I was confused about this the same as you as to why it is running after Windows already is loaded and the WinPE environment has already shutdown.

The WinPE image process for all other models that we have tested so far work as intended (I think 10 other models so far). I have not opened a ticket with Support yet for this reason (the problem is specific to the T470 at this time). There is definitely something odd about this particular Lenovo model that the WinPE process does not like and its frustrating that the answer is eluding me.
Dateianhänge
PreOS_PackageOrder.png
(64.45 KiB) 97-mal heruntergeladen
ConfigGroup.png
(132.57 KiB) 86-mal heruntergeladen

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 15. Feb 2019, 23:15

I am very curious. So the ..Host.log from WinPE time contains no errors and everything is fine and the ...Host_windows.log contains that error and the deployment cannot be completed?

Could you provide more from the _windows.log? Please remove sensitive information, if included. I would really like to see your log :)
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 15. Feb 2019, 23:36

I have the log from a P51 which I was just informed is having the same problems. so 2 out of 12 devices have this issue with the DiskPart now. Logs look to be similar to the T470. I cant seem to attach a txt of the log file to the post so converted it a pdf which is attached.

Thanks!
Dateianhänge
Matrix42.Platform.Service.Host_windows.pdf
(191.91 KiB) 80-mal heruntergeladen
Zuletzt geändert von ctearney am 18. Feb 2019, 15:34, insgesamt 1-mal geändert.

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 18. Feb 2019, 16:51

Hi,

what you can see in the _windows.log is, that there is no status file 'Computer.xml' available at that point:
2019-02-15 15:21:30.775 [Information] [PeAgent.GetPackagesToBeExecuted] File C:\UAF\Computer.xml does not exist. No package restriction.
That means, that the deployment or the execution of the PreOS packages will start from the beginning.
As that is the status file for the state of the installation of each package.

Check the folder 'EmpInst$\Wizard\OS\Auto\<your client's UUID or MAC>' for the file 'debug_<domain>_<clientName>.xml'!
That file might be there now. At Windows 10 time as it has been created again.
But is it there while you running the packages in WinPE?
What is the content of the file?

That should be on the assigned Empirum Depot server.
It might be that it is not synced? Or not even created while WinPE time!

REALLY looking forward to the LOG file from the WinPE runtime, please :D
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 19. Feb 2019, 00:38

Rumpelstilzchen, I sent you the debug_Matrix42.Platform.Service.Host.log & debug_Matrix42.Platform.Service.Host_windows.log files via PM from a newly imaged Lenovo T470 that I did this afternoon.

There is a twist now though, this time the laptop completed the WinPE image process successfully. I believe the reason for this is that I had deleted two Archived WIM files from the source directory that I put there which cleared about 8GB of space from the folder. When I compile a new Windows 10 build (I.e. each time a new version comes out I mount the WIM using DISM and make customizations to it like removing modern apps, customize wallpapers, add windows features, etc). The original WIM file is renamed to install.wim.orig or install.wim.rev1..etc... and kept in the source directory. I do this to keep track of my builds and typically has not been an issue.

When I was setting up my EPE image process for my 1809 build I was getting disk full errors on the allocated 12GB system partition (Empirum image system partition, not the OS system partition) so I archived off all but the current customized install.wim file. After doing this my EPE configuration worked successfully as expected. I then took the same laptop (a Lenovo T470) and tried imaging it with the WinPe process. This time it completed successfully. I then took another Lenovo T470 from inventory and imaged it the same way, it also completed successfully.

I went back and reimaged the first T470 via WinPE and got the same DiskPartitioning error that I have been getting but restarted the process again (for the 4th time) and it went thru successfully. I don't want to say the problem is fixed as I want to try a Lenovo P51 to see if it goes thru successfully, if it does than I think I can mark this as resolved but am still going to be confused as to why this was only happening with 2 models of laptops.

Benutzeravatar
Rumpelstilzchen
Beiträge: 36
Registriert: 25. Jan 2018, 16:15
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von Rumpelstilzchen » 19. Feb 2019, 11:27

Hi ctearney,

glad that you somehow make progress, but I am curious about the status xml more than about the WIM.

Once you've set your Empirum configuration and activated the client or group to be deployed (PXE booted),
the DDC of your client should NOT be changed by any process any more. As the TIMESTAMP of that file is logged inside the status XML.

On the runtime in WinPE I see inside the logs, that the times are diffrent. That is simply unexpected.
* Either there is a Filter Action set to change something on the configuration where the client is assigned (check where the client is assigned)
* or someone is changing the configuration while deployment is running. <- That really could be a reason.

Further you could check the Entry of DDC's timestamp inside the status XML and compare it with the timestamp of the DDC file it self.
Maybe there is some bug or issues with the time setting of the server and the time which is written inside the satus XML.

As I know newer version of Empirum Client Management (18.0.3 and higher) handle the timestamps diffrently:
The DDC timestamp is written inside computer INI for each PreOS package and that is exactly the timestamp which appears inside the status XML. <-- you might have to update to newer Empirum version if you have general TIME setting issues.

So check where the client is assigned. Check if filter actions going on. Make sure the DDC is not altered while deployment. Check the file time stamp of DDC and compare with status XML in MAC/UUID folder.
Update to Empirum 18.0.3.

:)
Heute backe ich morgen braue ich: Fehler könnten sich einschleichen und die Aussagen sind zu überprüfen - ich übernehme keine Verantwortung für das geschriebene Wort

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 19. Feb 2019, 14:51

Here are the contents of the status xml "debug_L-X-107785.xml". I am going to image another group of systems to confirm my results from yesterday, hopefully all is the same :-).

<?xml version="1.0" encoding="utf-8"?>
<ComputerOsPackageStatusList xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DdcTimeStamp>20190218-04:26:04.24</DdcTimeStamp>
<OsPackageStatusList>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\DiskPartitioning\3.9</PackageName>
<Status>Success</Status>
</OsPackageStatus>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\DriverIntegration\2.6</PackageName>
<Status>Success</Status>
</OsPackageStatus>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\WindowsInstallation\4.7</PackageName>
<Status>Success</Status>
</OsPackageStatus>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\PxeOffAndReboot\1.0</PackageName>
<Status>Success</Status>
</OsPackageStatus>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\DomainJoin\1.2</PackageName>
<Status>Success</Status>
</OsPackageStatus>
<OsPackageStatus>
<PackageName>Matrix42\OsPackages\EmpirumAgentSetup\1.6</PackageName>
<Status>RebootNeededImmediately</Status>
</OsPackageStatus>
</OsPackageStatusList>
</ComputerOsPackageStatusList>

Benutzeravatar
ctearney
Beiträge: 171
Registriert: 21. Feb 2014, 04:14
Wohnort: Dallas, Texas
Kontaktdaten:

Re: DiskPartitioning Failure

Beitrag von ctearney » 20. Feb 2019, 00:19

So I was able to reimage 2 T470s and 1 P51 successfully but then I pulled two separate x260 devices from inventory and tried imaging it but both received the DiskPartitioning error. Under the UUID folder located at Empirum\EmpInst\Wizard\os\Auto there are no XML files yet on the server as the image process does not get far enough along to create them. I can say with confidence that we don't have any action filters doing anything as we don't use them in our environment.

I may have to break down and have a ticket opened on this as it almost appears to be a moving target at this point. From look at the PXE logs, specifically the entry below timestamped 19.02.2019 16:39:29, its almost as if the PE packages are not being recorded as being successfully ran which I believe may be where you were going with the timestamp differences in the ini, ddc, and xml files.

The x260's I am working with now both had older bios versions loaded so I am updating those and trying again to see if that clears it since I was able to get past this with the T470 and P51 models I was working with originally.

19.02.2019 16:53:12 [PEAgent] [Windows] PreOS Package execution failure. Rebooting client in 300 seconds.
19.02.2019 16:53:11 [PEAgent] [Windows] Operation not supported on a critical disk.
Activity ID: {9aab93a2-aa9c-4961-a0ba-5a833c3faa42}
19.02.2019 16:53:05 [PEAgent] [Windows] Start to execute Matrix42\OsPackages\DiskPartitioning\3.9 package.
19.02.2019 16:39:29 [PEAgent] [WinPE] PE Agent error, rebooting client in 300 seconds.
19.02.2019 16:39:28 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\WindowsInstallation\4.7 package.
19.02.2019 16:31:19 [PEAgent] [WinPE] Using image file \\EMPIRUM.coserv.com\EmpInst$\Sys\win10\x64\pro\0_bc9fe15c-9045-46f4-b785-a6d69eb5c225\en-US\VISTADVD\install.wim.
19.02.2019 16:31:12 [PEAgent] [WinPE] Using default unattend.xml template.
19.02.2019 16:31:01 [PEAgent] [WinPE] Start to execute Matrix42\OsPackages\WindowsInstallation\4.7 package.
19.02.2019 16:30:57 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\DriverIntegration\2.6 package.
19.02.2019 16:30:56 [PEAgent] [WinPE] Using the drivers: '20F6006LUS-X260.zip' for vendor 'LENOVO' and model '20F6006LUS'.
19.02.2019 16:30:26 [PEAgent] [WinPE] Start to execute Matrix42\OsPackages\DriverIntegration\2.6 package.
19.02.2019 16:30:22 [PEAgent] [WinPE] Finished execution of Matrix42\OsPackages\DiskPartitioning\3.9 package.
19.02.2019 16:30:22 [PEAgent] [WinPE] Hard disk formating/partitioning successful.

Antworten

Zurück zu „OS-Installer“

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 1 Gast