I have been trying to get windows 8.1 to force into a blue screen, but all of my attempts have failed. I don't really want to go into driver code or anything to do it, but just crash it using some sort of silly loop hole.
I tried creating the CrashOnCtrlScroll registry and it doesn't seem to work, even after restarting my computer. I also tried ending csrss, but microsoft has decided to let the user have no control and denies access at all costs (even after an informative prompt window).
I looked online for a while, but can't find anything on blue screening 8.1. It seems that everything out there is for 8 and below.
Notmyfault , a portable tool created by Microsoft's Mark Russinovich for the Windows Internals book will help you get a BSOD with more than a couple of ways (i.e High IRQ fault, hang IRP, stack trash, deadlock, etc)
Which registry key have you tried? There is different key location for PS2 and USB Keyboard.
USB Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid
Add DWORD32, name= CrashOnCtrlScroll, value =0x1
PS2 Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt
Add DWORD32, name= CrashOnCtrlScroll, value =0x1
Restart. Hold the RIGHT CTRL key and press SCROLL LOCK twice quicky.
Related
I installed vmware on my Window 8.1 HP Envy x360 PC in early december. Late december I noticed it was difficult using it as help files of any application in use just keeps sprouting up. Even when there are no applications in the window help files window shows up few minutes after a restart.
I tried many suggestions online: removing HP redundant programs, Cleaning the system of malware and spyware, reviewing/disabling accessibility settings, still no luck. I later learnt from someone's comment on one forum that he noticed this happened on his pcs with vmware installedI finally had to display window key since the behaviour was as though the window key was perpetually pressed down such that typing letter "n", "e" or the "delete" key opens the help file of the program in use or those of windows.
Now with window key disabled the situation relatively better as I can read on the pc and do some programming task; but I still get the randow opening of help files when I click "n", "e" or "delete" keys (imagine how difficult it is to type in MSWord under this situation). The exception is that this doesn't occur while using Firefox.
Any idea what's going on?
I discovered the behaviour was a mimicking of window shotcuts involving the window key. So to temporarily solve this (since I didn't want to uninstall vmware) was to disable window key. I found some registry script at http://johnhaller.com/useful-stuff/disable-windows-key which I used.
This helped but when using certain programs (chrome and MSWord) typing any of n, b or delete key launches the help file so I used AutoHotKey - autohotkey.com to write lines of script to disable any SHIFT key shortcut combination
I'm doing some driver development on my Windows machine and I've been wondering why pressing the PrtSc (print screen) button to take a screen capture seems to hang my machine. There are some forums that suggest this happens when the DEBUG boot option is set in Windows and that this is a panic/bug-check in the Windows kernel.
Is this a Windows bug? Or is this actually useful in some way, like in Linux where PrtSc/SysRq is actually a kernel interrupt key?
UPDATE #1: I'm using Windows 7 x64 Professional Build 7601.
https://msdn.microsoft.com/en-us/library/windows/hardware/ff541727(v=vs.85).aspx
You can disable the SYSRQ key by editing the registry. In the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters registry key, create a value named BreakOnSysRq and set it equal to DWORD 0x0. Then, restart the computer. After you have restarted the computer, you can press the SYSRQ key on the target computer's keyboard and it will not break into the kernel debugger.
Obviously, you're likely using a usb keyboard, so make sure to add the BreakOnSysRq = 0 value data pair to kbdhid\Parameters (and for good measure hidusb and kbdclass, not i8042prt. This will prevent the PrntScr key from being interpreted as SysRq.
This should be a simple question that should have a simple solution...yet nothing that I have tried works. My question is why? Is there a security feature in Microsoft preventing sending keys to "Security Windows"?
AutoiT attempt (does not work):
WindWait("Windows Security")
Send("{DOWN}")
Sleep(10)
Send("{ENTER}")
I have also tried/look at this question
I have tried to do this in C++ and in C# and I can only get the window to become the active window but when I send keys to it it ignores it.
Below are some of the places that I have look in order to suppress or automate this window:
Windows 7 - Disable signature verification of drivers
Permanently disable driver signature enforcement on Win 7 x64
How to disable driver signing in Windows 7 SP1
Disabling digital driver signing in Windows 7
Windows - Suppress "Windows can't verify the publisher of this driver software"
All "solutions" from the above links don't work. I have been searching for an answer for more than 2 days now.
If someone can tell a successfully way to suppress/automate this I (and everyone that wants to know how to do this too) will really appreciated.
Are you able to identify the window using the Win... functions? If so you could try using MouseClick:
$aPos = WinGetPos("Windows Security")
MouseClick("left", $aPos[0]+50, $aPos[1]+100)
First get the position of the window, then add some pixels so that when you do a right-click with the mouse you click the appropriate button. Of course you need to adjust the number of pixels to add to the x-/y-axis.
I know this is old, but I just came across this issue as well.
I was able to solve it by using the following once the window was active:
ControlClick("Windows Security", "", "[CLASS:Button;INSTANCE:2]")
It did not work if I included the TEXT:&Install this driver software anyway in the control ID.
How can I unlock the windows lockscreen with Delphi? I didn't found anything on Google or Stackoverflow. I already tried to enter my password using keybd_event but it seems like the events dont work on the lockscreen.
You cannot unlock the lock screen programmatically from user space. That is by design.
OK, let's clarify that. Using documented APIs, you cannot do this. You need to reverse engineer undocumented APIs as #Remko has done for his SasLibEx product.
Remko Weijnen has very interesting projects in this direction. He has released a command-line tool (Winstation Locker) which is capable to unlock local/remote Windows XP station, without knowing the password of the user who has locked the computer.
For Windows Vista and later he has developed SasLibEx** library which can unlock even specific terminal services sessions, again without username/password.
Both methods require you to have Administrative privileges/account at the destination computer.
PLEASE NOTE, all these tools use nasty hacks that may be considered illegal, inappropriate, intolerant or criminal(?). It should be discussed with your Clients/Employer and should be used with caution!
** SasLibEx is a commercial product
Steamlink (a piece of hardware that allows you to stream your steam games to a big screen) currently has an issue, that if your screen is in a different part of the house, in order to play you need to walk to your PC unlock it and then walk back to your big screen.
In order to make it less painful, people in the community came up with this script:
#powershell -NoProfile -ExecutionPolicy unrestricted -Command "$sessionid=((quser $env:USERNAME | select -Skip 1) -split '\s+')[2]; tscon $sessionid /dest:console" 2> UnlockErrors.log
It can unlock your PC remotely. You can call tscon.exe from Delphi to emulate the same.
This actually can be done using powershell, psexec and windows onscreen keyboard. While a program cannot send input to winlogon, the windows osk can, and sure enough a program can send input to osk.
NOTE: The following is a remote solution.
As far as i know, Keyboard events wont work on lock screen unless you switch from Default Desktop to Winlogon desktop(Desktop referring to a container of all activities)
[Background]
Default desktop is the one you use when reading this post.
Winlogon would be the one that is set as active when you press Ctrl+Alt+Del
[XP]
You would need to Switch from Default to WinLogon Desktop[Check reference] and then you would be able to unlock machine by getting Window handle for Unlock Computer
IntPtr windowHandle = (IntPtr)FindWindow(null, "Unlock Computer");//Getting Window handle
Send username and password to respective edit boxes.
Reference
http://www.codeproject.com/Articles/16197/Remotely-Unlock-a-Windows-Workstation
[Win7]
Run tsdiscon.exe from remote. Not sure how this works; but for me, it unlocks the Locked Screen.
We have a counting meter hooked up to the serial port of a PC running Windows XP Embedded and everytime Windows starts, the meter starts clicking away about 90 times. We have tried using /fastdetect in boot.ini and it didn't work, even though it did work on XP Pro. We tried adding SkipEnumeration to the Device Parameter in the registry and it didn't work. When Plug&Play is disabled it won't click, but this isn't an option for us. Any other ideas? Thanks.
for anyone interested having this problem... I edited the Plug&Play registry and added a DependOnService multi-string with "Spooler" service as the data... this makes Plug&Play start later and allows enough time so that the meter isn't clicking crazy