[vbox-build-flare-vm.py] VM-Set-Legal-Notice shows an error
Open
@emtuls is already working on this.
Since Apr 25, 2025.
:bug: bug
:desktop_computer: virtualbox
- Dominant language
- PowerShell
- Stars
- 9.1k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Details
Executing VM-Set-Legal-Notice in vbox-build-flare-vm.py raises an error, although the legal notice is correctly set. Investigate why this happens to remove the error.
VM {2bc66f50-9ecb-4b10-a4dd-0cc329bc383d} 🚧 PS: VM-Set-Legal-Notice (Get-Content 'C:\Users\flare\Desktop\legal_notice_win10.txt' -Raw)
VM-Set-Legal-Notice : The term 'VM-Set-Legal-Notice' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
At line:1 char:1
+ VM-Set-Legal-Notice (Get-Content 'C:\Users\flare\Desktop\legal_notic ...
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (VM-Set-Legal-Notice:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
legalnoticecaption : Terms and Conditions
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\P
olicies\System
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\P
olicies
PSChildName : System
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
legalnoticetext :
The use of this VM requires that you have a license for Windows 10 Professional assigned to this
virtual machine (VM).
You must keep the '.dynamic' in the name and never change the host adapter settings to use this VM
for dynamic analysis.
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Poli
cies\System
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Poli
cies
PSChildName : System
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.