Prabhatkumar59

Hi @deonberlin - As I can observe from your issue description that the issue is mainly caused by the runtime identifier win7-x64. For the above, could you please try to:-...

Hi @deonberlin - Thank you for clarifying. Based on your input, this behavior does appear to be a breaking change introduced either by the new runner image or the .NET...

Hi @deonberlin - As the latest image version has been rolled out. Please update your sync process and try using the new version(20241211.1) and check once. Let us know if...

Hi @deonberlin - Since we haven't heard back, we'll assume your issue is resolved and will close this issue for now. Feel free to reach out to us for any...

Hi @ggkiokas - Thank you for bringing this issue to us. We are looking into this issue and will update you shortly on this issue after investigating.

@ggkiokas - Thanks for your response:) In order to switch to larger runners on GitHub Actions, especially when you're facing CPU and disk space limitations, you need to make some...

Hi @ggkiokas- Thanks for responding To address your concerns regarding the use of larger GitHub Actions runners within the Seafair organisation, here are some steps and clarifications:- **Availability and Cost**:-...

Hi @ggkiokas- The link you shared above(https://github.com/Seafair/poseidon/actions/runners), I do not have access of this actually. So, unable to check. And in order to contact GitHub Support, you can try using...

@pbk8s We are looking into the issue, we will get back to you after investigating this issue, Thanks.

@pbk8s , It seems it's an authentication issue. When using Packer to build a Windows 11 image in Azure, the provisioning process with PowerShell gets stuck on the command **bcdedit.exe...