I am trying to develop a new driver based on minispy code. I have successfully install minispy on my windows 11 (Surface computer) But i am trying to install the driver also on a window 10 (HP) and a Windows 11 dev (VM created with hyper-V) but it doesn't work... I have found the base code in this link : https://github.com/microsoft/windows-driver-samples/tree/main/filesys/miniFilter/minispy
after that i build it in Realease mode with visual studio 22 17.1.7 and i tried to install it by right-clicking on the minispy.inf and on install.
After this part I see minispy when i am running the command
driverquery
in my computers and VM, but when i am trying to start the service by running in an administrator command prompt
net start minispy
I get this result on my VM and my windows 10 computer (translate form french) :
error system 127
the procedure is unfindable
I don't really know what are the differences and I am feeling kind of lost here... If someone can help me i would be very happy!
Related
I'm running Windows 10 with WSL2. I'm using VSCode with the Remote - WSL extension to open the files from my wsl file system.
When I boot my Windows laptop, and open VSCode I get the following error:
When I perform a wsl.exe --shutdown in PowerShell, and restart Docker Desktop, Everything works fine. But I have to do this after every laptop restart.
Remote WSL extension version: v0.51.4
Visual Studio Code version: v1.51.1
Windows version: 10.0.19041 Build 19041
Someone any idea?
I have had this problem several times, and I have found that on Windows 10 20H2 one of the two options described below solves the problem.
Network reset
This option can make you lose your network configuration, so use it with discretion and read every warning. You can perform this task by going to Settings > Network & Internet > Status. There you need to click on the option "Network reset" after that, you can start the network reset by clicking on "Reset now" Picture of Windows 10 20H2 status section. Then you will need to wait some minutes until your PC is restarted automatically and try to execute Visual Studio Code under WSL2 again.
Reset Windows
This option is dangerous as it will remove either all your files and programs or all your installed programs. You select what you want to remove before starting the reset process. This option can be performed by going to Settings > Update & Security > Recovery. Then you have to click on the button "Get started" on the section "Reset this PC" and follow the instructions provided by the reset tool Picture of Windows 10 20H2 recovery section. After your Windows is reset, you will have to configure your WSL again because all your WSL files will be lost when executing this operation.
I am getting to know the HLK Studio and have run the recommended tests against one of our drivers ( a USBStorageFilter driver). When the driver was selected in the list of available components on the test machine the studio recommended the "HyperVisor Code Integrity Readiness Test" and the "TDI Filters and LSPS are not allowed" only. These ran without error and the studio is now showing test status of total 2 & passed 2.
However the PACKAGE tab is greyed out and will not allow me to proceed in creating the package for submission. There is no indication of any other steps and the documentation suggests that once the selected tests have completed you should be able to move on to the Package tab.
Anyone got any clues as to what is preventing this from happening?
Windows 10 Pro x64 16209 target machine, 2016 server (hperv) as the HLK server studio machine.
Thanks
Nick
I had the exact same issue and the only thing I did was exit HLK and start it again. It remembered the results and the Package tab wasn't greyed out anymore. I was able to continue with package creation.
My machine is HP EliteBook 8540w which supports Hyper-V as far as I know and I have enabled it in BIOS. However, I am receiving the following error when trying to start emulator for Windows Phone apps in Visual Studio 2015:
Windows Phone Emulator is unable to start because the hypervisor is not running.
The more detailed screen shot follows:
According to my i7-720QmCPU specs, it supports VT-d
So what is the reason for it being unable to start the emulator on my machine?
Update:
I also checked using the BIOS settings using coreinfo tool with the results as in the following picture:
Update:
Following stijnvangaal's comment, I ran the following command as administrator and rebooted.
'bcdedit /set hypervisorlaunchtype auto'
But, in the wake of next run I faced the following Window ("Virtual machine service not running")
Then, I started this (by clicking the link on the message box):
Under, action menu, I clicked "start service" and then ran the application again in visual studio. Success? Not yet unfortunately, ending up in this (feeling desperate):
I had the same issue :
1 - I disable the Hyper V mode in the Windows Feature :
Go to ‘Programs and Features’.
Select Turn Windows Features on or off.
Deselect Hyper-V and click OK.
2 - Restart the computer
3 - Enable Hyper V again in the Windows Feature.
And it works !
Hope it help :)
Just disable Hyper-V on "Programs and Features" (if it is enabled). Then restart computer and turn it on again. Problem solved for me
During the App Packaging and Deployment for Universal Windows Apps presentation (fast forward to 00:36:00) one specific command line utility - WinAppDeployCmd - was used for deployment Windows 10 Universal application to the phone running Windows 10 Mobile. This utility could be found here:
"c:\Program Files (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe"
But every time I'm trying to deploy sample .appx package to the Lunia 635 phone with Windows Mobile v10.0.12562.84 or Surface 3 device with Windows 10 Pro Insider Preview (all devices on the same network as my dev machine) - I'm getting the same "connection failed" error:
Windows App Deployment Tool Version
10.0.0.0 Copyright (c) Microsoft
Corporation. All rights reserved.
Opening connection to device at '192.168.1.139'.
0x80131500 - Connection Failed
0x800705B4 - Timed out waiting for
network events.
Just in case - I could ping both of the devices from my dev machine without problem and can also deploy to any of them from VS2015RC (also tried with renamed WinAppDeployCmd.exe - to make sure that VS2015RC doing deployment somehow differently without using this tool).
So, I'm wondering - are there anyone who succeeded with app deployment using WinAppDeployCmd.exe?
This is a known issue in the current release. There is no workaround and it will light up in a future Windows 10 Insider Preview SDK and tools release.
https://social.msdn.microsoft.com/Forums/en-US/5c8d6f20-699c-4da2-9460-f73e89bf27c3/known-issue-cannot-sideload-applications-using-winappdeploycmd-windows-10-insider-preview-sdk-and?forum=Win10SDKToolsIssues
I have succeeded to deploy an .appx using the WinAppDeployCmd command line tool. Probably the issue have been correct at the latest versions.
For the ones that are not familiar with this tool, it allows you to deploy an Universal Windows app from a Windows 10 machine to any Windows 10 Mobile device via USB or WiFi (since they're on the same subnet). That's a perfect solution if you doesn't have Visual Studio, doesn't have the app source code or if you're under a Hyper-V Virtual Machine.
Basically you will need:
Windows 10 SDK
Generate the .appx package (PC)
Enable the developer mode (Mobile)
Turn on the discovery mode (Mobile)
Get the code to pair devices (Mobile)
Get mobile IP address using WinAppDeployCmd tool (PC)
Run command (PC)
The command will look like this
WinAppDeployCmd install -file “<path>” -ip <ip> -pin <pin>
The tool can be found at C:\Arquivos de Programas (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe
You can find a detailed step-by-step tutorial here
This happened to me once when the USB socket was faulty and Windows compained about the device not being recognized. I switched sockets and everything worked. So make sure you try other sockets (or even a different computer, to rule out the specific machine).
This tool let's you install but does not run the app after install like it did the first version in windows 8.1
I'm attempting to get the Modern IE VM for Windows 10 with IE 11 to run in Parallels 10.2 on Mac OS X 10.10.3. I have downloaded it multiple times, using both the single zip and multiple file methods. When I start it I get
Recovery Your PC/Device needs to be repaired.
The digital signature couldn't be verified.
File: \Windows\system32\winload.exe
Error code: 0xc0000428
Press Enter to try again. Press F8 for Startup Settings.
No action that I can take will allow this to function.
I should note that I have most (all?) of the other VMs installed, and they all work fine.
This suggests it has something to do with time: http://www.tomshardware.co.uk/forum/id-2636035/winload-exe-verified-error-code-0xc0000428.html
Setting my host systems time to something before April 15th worked for me.