Global error at creating WinPE Boot Configuration

Moderator: jknoth

Post Reply
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Global error at creating WinPE Boot Configuration

Post by alukic » 22. Feb 2019, 16:31

Hallo,

wir waren gestern beim ExperienceDay in Wien und haben uns das Deployment mit WinPE angesehen und wollten das natürlich gleich bei uns ausprobieren. Leider bekommen wir einen Fehler der nicht so simple ist kann uns hier wer helfen.

Code: Select all

2019-02-22 11:24:57.793 ThreadId=22988 [PE] [Powershell] ----------------------------------------
2019-02-22 11:24:57.793 ThreadId=24788 [PE] [Powershell] Starting CreatePXEWinPEMultiPlatform.ps1
2019-02-22 11:24:57.793 ThreadId=24788 [PE] [Powershell] ----------------------------------------
2019-02-22 11:24:57.797 ThreadId=24788 [PE] [Powershell] 
2019-02-22 11:24:57.797 ThreadId=24788 [PE] [Powershell] Friday, February 22, 2019 11:24:57 AM
2019-02-22 11:24:57.800 ThreadId=24788 [PE] [Powershell] Using folder C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300
2019-02-22 11:24:57.810 ThreadId=24788 [PE] [Powershell] Using EFI x64 pre-boot architecture: True
2019-02-22 11:24:57.811 ThreadId=24788 [PE] [Powershell] Using EFI x86 pre-boot architecture: False
2019-02-22 11:24:57.811 ThreadId=24788 [PE] [Powershell] Using BIOS x64 pre-boot architecture: False
2019-02-22 11:24:57.812 ThreadId=24788 [PE] [Powershell] Using BIOS x86 pre-boot architecture: False
2019-02-22 11:24:57.826 ThreadId=22988 [PE] [Powershell] Using ram disk tftp block size: 4096
2019-02-22 11:24:58.007 ThreadId=22988 [PE] [Powershell] Using Windows ADK path 'C:\Program Files (x86)\Windows Kits\10\' from registry.
2019-02-22 11:24:58.612 ThreadId=24788 [PE] [Powershell] ------------------------------------------
2019-02-22 11:24:58.613 ThreadId=24788 [PE] [Powershell] Create image for architecture Efi64
2019-02-22 11:24:58.614 ThreadId=24788 [PE] [Powershell] Friday, February 22, 2019 11:24:58 AM
2019-02-22 11:24:58.621 ThreadId=18176 [PE] [Powershell] Using Windows ADK path 'C:\Program Files (x86)\Windows Kits\10\' from registry.
2019-02-22 11:24:58.622 ThreadId=18176 [PE] [Powershell] Using folder C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXE\efix64
2019-02-22 11:24:59.400 ThreadId=22988 [PE] [Powershell] Creating C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXE\efix64
2019-02-22 11:24:59.405 ThreadId=22988 [PE] [Powershell] Creating C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXEMount
2019-02-22 11:24:59.408 ThreadId=22988 [PE] [Powershell] Copy winpe source files amd64 - C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXE\efix64
2019-02-22 11:25:00.778 ThreadId=18176 [PE] [Powershell] Copy BCD \\SERVER\EmpInst$\Sys\Images\WinPE to C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXE\efix64
2019-02-22 11:25:00.832 ThreadId=22988 [PE] [Powershell] BcdEdit set ram disk tftp block size to: 4096
2019-02-22 11:25:01.063 ThreadId=22988 [PE] [Powershell] The operation completed successfully.
2019-02-22 11:25:03.288 ThreadId=22988 [PE] [Powershell] Creating new wim file.
2019-02-22 11:25:03.290 ThreadId=22988 [PE] [Powershell] Mount C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\WinPEPXE\efix64\sources\boot.wim file
2019-02-22 11:25:31.803 ThreadId=24788 [PE] [Powershell] ########## Global error at creating WinPE Boot Configuration ##########
2019-02-22 11:25:31.831 ThreadId=24788 [PE] [Powershell] 
2019-02-22 11:25:31.832 ThreadId=24788 [PE] [Powershell] Mount-WindowsImage : 
2019-02-22 11:25:31.832 ThreadId=24788 [PE] [Powershell] At \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1:190 char:5
2019-02-22 11:25:31.832 ThreadId=24788 [PE] [Powershell] +     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Ind ...
2019-02-22 11:25:31.832 ThreadId=11024 [PE] [Powershell] +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-02-22 11:25:31.832 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.855 ThreadId=11024 [PE] [Powershell] System.Runtime.InteropServices.COMException (0x80070005): Access is denied.
2019-02-22 11:25:31.855 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.855 ThreadId=11024 [PE] [Powershell]    at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
2019-02-22 11:25:31.861 ThreadId=11024 [PE] [Powershell] ########## Detailed information:
2019-02-22 11:25:31.861 ThreadId=11024 [PE] [Powershell] ########## ErrorRecord object:
2019-02-22 11:25:31.864 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.865 ThreadId=24788 [PE] [Powershell] 
2019-02-22 11:25:31.865 ThreadId=24788 [PE] [Powershell] 
2019-02-22 11:25:31.865 ThreadId=24788 [PE] [Powershell] 
2019-02-22 11:25:31.892 ThreadId=11024 [PE] [Powershell] PSMessageDetails      : 
2019-02-22 11:25:31.892 ThreadId=11024 [PE] [Powershell] Exception             : System.Runtime.InteropServices.COMException (0x80070005): Access is denied.
2019-02-22 11:25:31.892 ThreadId=11024 [PE] [Powershell]                         
2019-02-22 11:25:31.892 ThreadId=11024 [PE] [Powershell]                            at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord 
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell]                         errorRecord)
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell] TargetObject          : 
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell] CategoryInfo          : NotSpecified: (:) [Mount-WindowsImage], COMException
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell] FullyQualifiedErrorId : Microsoft.Dism.Commands.MountWindowsImageCommand
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell] ErrorDetails          : 
2019-02-22 11:25:31.893 ThreadId=11024 [PE] [Powershell] InvocationInfo        : System.Management.Automation.InvocationInfo
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell] ScriptStackTrace      : at CreateWimFile, \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: 
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         line 190
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         at CreatePXEWinPE, \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: 
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         line 441
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         at Startup, \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: line 524
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         at <ScriptBlock>, \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: 
2019-02-22 11:25:31.894 ThreadId=11024 [PE] [Powershell]                         line 574
2019-02-22 11:25:31.895 ThreadId=11024 [PE] [Powershell]                         at <ScriptBlock>, <No file>: line 1
2019-02-22 11:25:31.895 ThreadId=11024 [PE] [Powershell] PipelineIterationInfo : {}
2019-02-22 11:25:31.895 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.895 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.895 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.896 ThreadId=11024 [PE] [Powershell] ########## Invocation info:
2019-02-22 11:25:31.897 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.897 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.903 ThreadId=11024 [PE] [Powershell] MyCommand             : Mount-WindowsImage
2019-02-22 11:25:31.903 ThreadId=11024 [PE] [Powershell] BoundParameters       : {}
2019-02-22 11:25:31.903 ThreadId=11024 [PE] [Powershell] UnboundArguments      : {}
2019-02-22 11:25:31.903 ThreadId=11024 [PE] [Powershell] ScriptLineNumber      : 190
2019-02-22 11:25:31.903 ThreadId=11024 [PE] [Powershell] OffsetInLine          : 5
2019-02-22 11:25:31.904 ThreadId=11024 [PE] [Powershell] HistoryId             : 1
2019-02-22 11:25:31.904 ThreadId=11024 [PE] [Powershell] ScriptName            : \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1
2019-02-22 11:25:31.904 ThreadId=11024 [PE] [Powershell] Line                  :     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Index $WinPeImageIndex -Path 
2019-02-22 11:25:31.904 ThreadId=11024 [PE] [Powershell]                         $MountPxeDir -LogLevel Warnings -LogPath $LogFileDism
2019-02-22 11:25:31.904 ThreadId=11024 [PE] [Powershell]                         
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] PositionMessage       : At \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1:190 char:5
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell]                         +     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Ind ...
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell]                         +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] PSScriptRoot          : \\SERVER\EmpInst$\Sys\Images\WinPE
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] PSCommandPath         : \\SERVER\EmpInst$\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] InvocationName        : Mount-WindowsImage
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] PipelineLength        : 0
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] PipelinePosition      : 0
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] ExpectingInput        : False
2019-02-22 11:25:31.905 ThreadId=11024 [PE] [Powershell] CommandOrigin         : Internal
2019-02-22 11:25:31.906 ThreadId=11024 [PE] [Powershell] DisplayScriptPosition : 
2019-02-22 11:25:31.906 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.906 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.906 ThreadId=11024 [PE] [Powershell] 
2019-02-22 11:25:31.967 ThreadId=15276 [PE] Finished Powershell process.
2019-02-22 11:25:31.967 ThreadId=15276 [PE] Exit code = 1
2019-02-22 11:25:31.970 ThreadId=15276 [PE] Error at executing powershell script, check dism log file: C:\Users\svc_empservices\AppData\Local\Temp\CreateBootImageWinPe\30300\CreatePXEWinPeDism.log
2019-02-22 11:25:31.970 ThreadId=15276 [PE] => UPDATE ENTRY:2478841 STATE:Failure MSG:'Error at executing powershell script.' EXCEPTION:The powershell script execution at creating the pxe image was not successful. Detailed information at BackendTaskQueueHost logging file.
2019-02-22 11:25:31.988 ThreadId=15276 [PE] Finished ProcessJob with result -1
lg Anel
Top
User avatar
Hendrik_Ambrosius
Moderator
Moderator
Posts: 7965
Joined: 13. Dec 2004, 23:10
Location: Adendorf/Lüneburg

Re: Global error at creating WinPE Boot Configuration

Post by Hendrik_Ambrosius » 22. Feb 2019, 16:44

Es steht ja dort: "Detailed information at BackendTaskQueueHost logging file"
Was steht denn darin?
Hendrik Ambrosius / Senior Presales Consultant
Mobile: +49 172 408 4447 | hendrik.ambrosius@matrix42.com
Matrix42 GmbH | Elbinger Straße 7 | 60487 Frankfurt am Main | Germany | www.matrix42.com

Disclaimer: I participate in this forum on a voluntary basis. Views expressed are not necessarily those of Matrix42 or of the support team.
Top
User avatar
Rumpelstilzchen
Posts: 36
Joined: 25. Jan 2018, 16:15
Contact:
Contact Rumpelstilzchen

Re: Global error at creating WinPE Boot Configuration

Post by Rumpelstilzchen » 22. Feb 2019, 16:54

Hallo Anel,

das Skript wird vom BTQH-Dienst (Back-end task queue) ausgeführt.
Wie es aussieht hat es nicht genügend Rechte und damit auch das Skript.

Der Eintrag, dass im anderen Log etwas Detailiertes steht, ist nicht ganz richtig - das ist der detailierte Log - denke ich.

Hat der Benutzer unter dem der Dienst (Empirum-Backend Task Queue Host) läuft genügend Rechte? Um Mount-WindowsImage auf das *.wim-File aufzurufen?

Im DBUtil gibt es die Installation Log On und Service Log On-Tabs. Dort kann man für den Empirum-Activation-Dienst Benutzer vergeben.
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
Top
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Re: Global error at creating WinPE Boot Configuration

Post by alukic » 25. Feb 2019, 09:07

Hallo,

vielen danke für die schnellen Antworten.

Zu dem Log, ja das ist schon das detaillierte :-)
Zum den Rechten, ja der User hat Zugriff auf den Ordner. Ich hab das Script auch mit meinem Domain Admin probiert und dort bekomme ich den gleichen Fehler. Denke also nicht das es an den Rechten liegt.

Kann es vielleicht sein dass das Script nur mit einer bestimmten WAIK version arbeiten kann? Ansonsten fällt mir hier nichts ein was es noch sein könnte.

lg Anel
Top
User avatar
Rumpelstilzchen
Posts: 36
Joined: 25. Jan 2018, 16:15
Contact:
Contact Rumpelstilzchen

Re: Global error at creating WinPE Boot Configuration

Post by Rumpelstilzchen » 25. Feb 2019, 10:18

Hi Anel,

es muss auch dafür gesorgt werden, dass der Benutzer das Skript mit "elevated rights/access" benutzten kann.
Der Benutzer unter welchem der BTQH-Dienst läuft sollte auch in der Gruppe der Lokalen Administratoren sein.

Ist die *.wim-Datei als "Read Only" markiert?

(Ansonsten vielleicht das WADK deinstallieren und nochmals installieren.)
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
Top
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Re: Global error at creating WinPE Boot Configuration

Post by alukic » 25. Feb 2019, 10:53

Anbei der output wenn ich das script mit meinem Domain Admin und elevated rights laufen lasse.

Code: Select all

PS D:\Empirum\EmpInst\Sys\Images\WinPE> .\CreatePXEWinPEMultiPlatform.ps1
----------------------------------------
Starting CreatePXEWinPEMultiPlatform.ps1
----------------------------------------

Montag, 25. Februar 2019 10:52:00
Using folder D:\Empirum\EmpInst\Sys\Images\WinPE
Using EFI x64 pre-boot architecture: True
Using EFI x86 pre-boot architecture: False
Using BIOS x64 pre-boot architecture: False
Using BIOS x86 pre-boot architecture: False
Using ram disk tftp block size: 0
Using Windows ADK path 'C:\Program Files (x86)\Windows Kits\10\' from registry.
------------------------------------------
Create image for architecture Efi64
Montag, 25. Februar 2019 10:52:01
Using Windows ADK path 'C:\Program Files (x86)\Windows Kits\10\' from registry.
Using folder D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64
Removing D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64
Removing D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXEMount
Creating D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64
Creating D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXEMount
Copy winpe source files amd64 - D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64
Copy BCD D:\Empirum\EmpInst\Sys\Images\WinPE to D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64
Creating new wim file.
Mount D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64\sources\boot.wim file
########## Global error at creating WinPE Boot Configuration ##########

Mount-WindowsImage :
At D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1:190 char:5
+     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Ind ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

System.Runtime.InteropServices.COMException (0x80070005): Access is denied.

   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
########## Detailed information:
########## ErrorRecord object:




PSMessageDetails      :
Exception             : System.Runtime.InteropServices.COMException (0x80070005): Access is denied.

                           at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord
                        errorRecord)
TargetObject          :
CategoryInfo          : NotSpecified: (:) [Mount-WindowsImage], COMException
FullyQualifiedErrorId : Microsoft.Dism.Commands.MountWindowsImageCommand
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at CreateWimFile, D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: line 190
                        at CreatePXEWinPE, D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: line
                        443
                        at Startup, D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: line 526
                        at <ScriptBlock>, D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1: line 576
                        at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}



########## Invocation info:


MyCommand             : Mount-WindowsImage
BoundParameters       : {}
UnboundArguments      : {}
ScriptLineNumber      : 190
OffsetInLine          : 5
HistoryId             : 2
ScriptName            : D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1
Line                  :     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Index $WinPeImageIndex -Path
                        $MountPxeDir -LogLevel Warnings -LogPath $LogFileDism

PositionMessage       : At D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1:190 char:5
                        +     Mount-WindowsImage -ImagePath "$WorkPxeDir\sources\boot.wim" -Ind ...
                        +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PSScriptRoot          : D:\Empirum\EmpInst\Sys\Images\WinPE
PSCommandPath         : D:\Empirum\EmpInst\Sys\Images\WinPE\CreatePXEWinPEMultiPlatform.ps1
InvocationName        : Mount-WindowsImage
PipelineLength        : 0
PipelinePosition      : 0
ExpectingInput        : False
CommandOrigin         : Internal
DisplayScriptPosition :



PS D:\Empirum\EmpInst\Sys\Images\WinPE>
Wenn ich mir den "Mount-WindowsImage" Befehl selber zusammen baue bekomme ich auch den gleichen fehler mit Access Denied.
Top
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Re: Global error at creating WinPE Boot Configuration

Post by alukic » 25. Feb 2019, 11:01

Hier der output aus dem selber zusammen gebauten Mount-WindowsImage Befehl.

Code: Select all

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\a-aluki> Mount-WindowsImage -ImagePath "D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXE\efix64\sources\boot.wim
" -Index 1 -Path "D:\Empirum\EmpInst\Sys\Images\WinPE\WinPEPXEMount"
Mount-WindowsImage : Access is denied.
At line:1 char:1
+ Mount-WindowsImage -ImagePath "D:\Empirum\EmpInst\Sys\Images\WinPE\Wi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Mount-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.MountWindowsImageCommand

PS C:\Users\a-aluki>
Top
User avatar
Rumpelstilzchen
Posts: 36
Joined: 25. Jan 2018, 16:15
Contact:
Contact Rumpelstilzchen

Re: Global error at creating WinPE Boot Configuration

Post by Rumpelstilzchen » 25. Feb 2019, 11:04

Is Read Only auf der Datei *.wim? Fals aj, Entferne und probiere es nochmal!
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
Top
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Re: Global error at creating WinPE Boot Configuration

Post by alukic » 25. Feb 2019, 11:07

Also mit dem GUI Tool welches auch die PS Befehle benutzt geht es auch nicht, aber hier sehe ich zumindest bei welcher Datei es Probleme gibt.

Image

Ich vermute jetzt mal das es unser Anti-Virus ist.
Top
User avatar
Rumpelstilzchen
Posts: 36
Joined: 25. Jan 2018, 16:15
Contact:
Contact Rumpelstilzchen

Re: Global error at creating WinPE Boot Configuration

Post by Rumpelstilzchen » 25. Feb 2019, 11:11

Ohhh... Klasse. Das könnte ja wirklich sein! Anti Virus.
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
Top
User avatar
alukic
Posts: 11
Joined: 27. Mar 2018, 10:18
Location: Vienna
Contact:
Contact alukic

Re: Global error at creating WinPE Boot Configuration

Post by alukic » 25. Feb 2019, 11:13

Ok, also es ist Fix der Anti-Virus.

Hier mal ein kurzer Auszug aus dem Log.

Code: Select all

.06.2018 23:00:19   mfeesp(6348.3308) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:19   mfeesp(6348.14244) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:19   mfeesp(6348.14244) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:19   mfeesp(6348.14244) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:19   mfeesp(6348.3308) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:22   mfeesp(6348.14244) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:45   mfeesp(6348.13992) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_6.1.7601.17514_NONE_B709E946FAB5388D, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:45   mfeesp(6348.13992) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-LSA_31BF3856AD364E35_6.1.7601.17514_NONE_04709031736AC277, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:46   mfeesp(6348.13992) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-SERVICES-SVCHOST_31BF3856AD364E35_6.1.7601.17514_NONE_13E15F101BED4826, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:46   mfeesp(6348.3308) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-SMSS_31BF3856AD364E35_6.1.7601.17514_NONE_0A60AD6C2FD129FB, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
14.06.2018 23:00:46   mfeesp(6348.13992) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-WINLOGON_31BF3856AD364E35_6.1.7601.17514_NONE_CDE90685EB910636, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.7068) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.7068) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.4220) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.6788) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.4076) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:05   mfeesp(3308.4220) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\SYSTEM32, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:27   mfeesp(3308.4220) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_6.1.7601.17514_NONE_B709E946FAB5388D, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:27   mfeesp(3308.4220) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-LSA_31BF3856AD364E35_6.1.7601.17514_NONE_04709031736AC277, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:29   mfeesp(3308.4220) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-SERVICES-SVCHOST_31BF3856AD364E35_6.1.7601.17514_NONE_13E15F101BED4826, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:29   mfeesp(3308.4076) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-SMSS_31BF3856AD364E35_6.1.7601.17514_NONE_0A60AD6C2FD129FB, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
15.06.2018 02:00:29   mfeesp(3308.4076) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran RSYNC.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\WINPE\X64\3.0\PESOURCE\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-WINLOGON_31BF3856AD364E35_6.1.7601.17514_NONE_CDE90685EB910636, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
01.02.2019 12:25:36   mfeesp(2576.12972) <SYSTEM> ApBl.AP.Activity: NT AUTHORITY\SYSTEM ran SYSTEM:REMOTE, which tried to access D:\EMPIRUM\CONFIGURATOR\PACKAGES\MICROSOFT\WINDOWS 10 ENTERPRISE FEATURE UPGRADE\1809\FILES, violating the rule "Remotely creating autorun files", and was blocked. For information about how to respond to this event, see KB85494.
22.02.2019 11:25:25   mfeesp(2576.16844) <SYSTEM> ApBl.AP.Activity: GTOFFICE\svc_empservices ran POWERSHELL.EXE, which tried to access C:\USERS\SVC_EMPSERVICES\APPDATA\LOCAL\TEMP\CREATEBOOTIMAGEWINPE\30300\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
22.02.2019 11:26:06   mfeesp(2576.16844) <SYSTEM> ApBl.AP.Activity: GTOFFICE\svc_empservices ran POWERSHELL.EXE, which tried to access C:\USERS\SVC_EMPSERVICES\APPDATA\LOCAL\TEMP\CREATEBOOTIMAGEWINPE\30301\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
22.02.2019 15:56:18   mfeesp(2576.11484) <SYSTEM> ApBl.AP.Activity: GTOFFICE\svc_empservices ran POWERSHELL.EXE, which tried to access C:\USERS\SVC_EMPSERVICES\APPDATA\LOCAL\TEMP\CREATEBOOTIMAGEWINPE\30302\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
25.02.2019 10:52:29   mfeesp(2576.24424) <SYSTEM> ApBl.AP.Activity: GTOFFICE\a-aluki ran POWERSHELL.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\IMAGES\WINPE\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
25.02.2019 11:01:03   mfeesp(2576.11712) <SYSTEM> ApBl.AP.Activity: GTOFFICE\a-aluki ran POWERSHELL.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\IMAGES\WINPE\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
25.02.2019 11:03:39   mfeesp(2576.24424) <SYSTEM> ApBl.AP.Activity: GTOFFICE\a-aluki ran DISM++X64.EXE, which tried to access D:\EMPIRUM\EMPINST\SYS\IMAGES\WINPE\WINPEPXEMOUNT\WINDOWS\WINSXS\AMD64_MICROSOFT-WINDOWS-CSRSS_31BF3856AD364E35_10.0.15063.0_NONE_69F7BD111CE467B4, violating the rule "Modifying core Windows processes", and was blocked. For information about how to respond to this event, see KB85494.
Vielleicht Hilft das hier jemand anderen schneller den Fehler zu finden.

Vielen Dank für eure Unterstützung.

:oops: :oops: :oops:
Top
User avatar
Rumpelstilzchen
Posts: 36
Joined: 25. Jan 2018, 16:15
Contact:
Contact Rumpelstilzchen

Re: Global error at creating WinPE Boot Configuration

Post by Rumpelstilzchen » 25. Feb 2019, 11:15

Klar, es hilft uns allen hier weiter. Wenn jemand wieder mal auf soetwas trifft!

Danke dir! Super!
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
Top
Post Reply

Return to “OS Installer”

Who is online

Users browsing this forum: No registered users and 1 guest