Trying to test a new CSP under Win 7. Set the boot config to allow kernel debug, run WndDbg and select file:kernel debug and set to local. Attempting to use signtool with my new CSP still results in signature failure check. Environment is:
OS Name: Microsoft Windows 7 Home Premium
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Model: Dell System Inspiron N7110
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2501 Mhz
BIOS Version: Dell Inc. A09, 11/18/2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Any thoughts on why the presence of the kernel debugger is not preventing the signature check on the test CSP? Does that setup only work in a remote-debug environment?
You'll need a remote debugger to disable the signature check.
There are various mechanisms such as 1394 (FireWire) or Serial Cable by which you can can connect the second computer for remote debugging.
If your CSP can run in a VM, then that would be an option too if you just have the one machine.
Related
npm install
audited 17250 packages in 7.466s
26 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
My System Info:
1.OS Name Microsoft Windows 10 Home Single Language
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-7CV9HTK
System Manufacturer HP
System Model HP ENVY Laptop 13-ah1xxx
System Type x64-based PC
System SKU 5HZ05PA#AKL
Processor Intel(R) Core(TM) i7-8565U CPU # 1.80GHz, 1992 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Insyde F.12, 11/8/2018
SMBIOS Version 3.0
Embedded Controller Version 69.72
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 850B
BaseBoard Version 69.72
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.387"
User Name DESKTOP-7CV9HTK\Hanifullah Jamalzai
Time Zone Afghanistan Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.8 GB
Available Physical Memory 9.89 GB
Total Virtual Memory 18.2 GB
Available Virtual Memory 10.3 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Npm is recognized on cmd but not on vscode?
Assuming you are using windows, you need to update the path in environment/user variables AND restart vscode for it to recognize the changes.
I had Yarn Package Manager which is an alternative to npm. The packages you are trying to install can not be installed with npm, "npm install" will not work because it is not the format used by yarn when you are trying to install some package.
I just installed Rstudio on my windows 7 machine, while trying to launch the application for the 1st time I get the error message as “Application stopped running”, I was never able to launch the application.
Troubleshooting Steps followed
Check Graphic card drivers, updated the windows patches and all the drivers are up-to-date.
Checked the DLL files (ig75icd64.dll ), which also present in windows32 folder.
Uninstalled/reinstalled and rebooted the multiple time
R application is working fine, but not the Rstudio
Software Info:
R Version : 3.6.1
Rstudio : 1.2.5 (Desktop Version)
Now I need help in fixing the issue, Please advise!
Error Message are given below:
Problem signature
Problem Event Name: APPCRASH
Application Name: rstudio.exe
Application Version: 1.2.5019.0
Application Timestamp: 5db1e0e4
Fault Module Name: ig75icd64.dll
Fault Module Version: 10.18.10.4425
Fault Module Timestamp: 5702a9ad
Exception Code: c0000005
Exception Offset: 000000000017143a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: e52e
Additional Information 2: e52e2780b500f2b41eafa296aa17a677
Additional Information 3: 63be
Additional Information 4: 63bead1da0d8da840e5be281271dd92a
System Info
OS Name: Microsoft Windows 7 Professional
OS Version: 6.1.7601 Service Pack 1 Build 7601
System Type: x64-based PC
Chip type: Intel(R) HD Graphics Family
Current Mode: 1366 x 768 (32 bit) (50Hz)
Monitor Name: LCD 1366x768
Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32
Driver File Version: 10.18.0010.4425 (English)
Issue Fixed !
I used older Version 1.1.463 RStudio, Now i was able to launch the application on Windows 7
https://support.rstudio.com/hc/en-us/articles/206569407-Older-Versions-of-RStudio
I'm new on LG smart TV apps. I've installed the SDK provided by LG (Oracle Virtual Box, Safari, Eclipse, sdk itself).
Now everything is running, but when I try to launch the emulator, a remote control is displayed, and on the virtualbox window, I see an error and no emulator is launched.
This is my plataform:
Windows 7 on a intel i7, 8 gb ram
Virtual Box 4.1.18 (I've installed 4.2.4 before, but sdk installer replace it to 4.1.18)
Safari 5.1.7
Java JRE 1.6
LG Smart TV SDK 3.0.0
This is the log generated by Virtual Box:
VirtualBox 4.1.18 r78361 win.amd64 (Jun 5 2012 15:58:23) release log
00:00:05.144 Log opened 2015-09-28T15:09:54.564361900Z
00:00:05.144 OS Product: Windows 7
00:00:05.144 OS Release: 6.1.7601
00:00:05.144 OS Service Pack: 1
00:00:05.144 Host RAM: 7926MB RAM, available: 864MB
00:00:05.144 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:05.144 Process ID: 12536
00:00:05.144 Package type: WINDOWS_64BITS_GENERIC
00:00:05.145 Installed Extension Packs:
00:00:05.145 None installed!
00:00:05.156 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:05.439 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false
Is there any known issue about this? What is the reason because "Power up failed"? How can I fix the VM? Does this software really works on Windows?
Thanks!
I would try 4.2.18 and make sure you are installing the correct SDK for your OS (x64/x32).
You can uninstall VBox and reinstall if needed and again check your architecture
I'm trying to install Windows Server 2012 R2 on Virtualbox but I get this error all the time:
Proccessor: Intel(R) Core(TM) i5 CPU
System type: 64-bit
ISO file: en_windows_server_2012_x64_dvd_915478.iso
I've tried many things and had no result, I tried on another computer but got the same error.
When creating a new VirtualMachine I used "Windows > Other Windows" and created a new VDI
Common problem. You have to activate virtualization in your bios. If doesn't matter if you have a 64 bits CPU if you don't have the virtualization activated. This is an example.
I have working
kernel debug setup on old host computer with Windows Xp. On the new computer i
get preinstalled Win 7. I have installed PCI to Firewire card (usb-5pci3pfw).I
have installed WinDDK (7600.16385.1).
So I go to
C:\WinDDK\7600.16385.1\Debuggers and run as administrator windbg.exe
(6.12.2.633)
Choose File
> Kernel Debugging > 1394 > and select channel like on target and get
this message:
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\SysNative\drivers\1394kdbg.sys.
Cannot install a 32 bit driver on a 64 bit host.
Please run the 64 bit native version of this debugger to
upgrade to the latest version of 1394kdbg.sys.
Kernel debugger failed initialization, HRESULT 0x80004005
"Unspecified error"
I expect that
WinDbg will make install of the 1394kdbg.sys driver.
Yes in C:\WinDDK\7600.16385.1\Debuggers\1394 directory there 1394kdbg.sys and
1394dbg.inf.
In inf file
there install section only for 32 bit.
I try to add
64 bit section and install driver but it doesn't helps.
Does somebody know the right way to
install kernel debugging on Win 7 64 bit Host?
You have to install and use the x64 debugging tools.
These should be part of the Windows SDK.
So yes install of "Debugging Tools for Windows (x64)" did help.
I downloaded Windows SDK as Christopher wrote.
Selected install of debug tools, i did have some problems during installation because i have installed Visual Studio Compilers so i use Help from Here
Then Windows SDK copy installation .msi files here:
"C:\Program Files\MicrosoftSDKs\Windows\v7.1\Redist\Debugging Tools for Windows"
In this folder:
dbg_amd64.msi - (64 bit version of debuging tools)
dbg_ia64.msi - (for Itanium processors)
dbg_x86.msi - (32 bit version of debugging tools)
i install "dbg_amd64.msi" and get 64bit debugging tools folder here:
"C:\Program Files\Debugging Tools for Windows (x64)"
now in 1394 subfolder there "1394kdbg.sys" and "1394dbg.inf" for 64bit.
so now i connect my host win7 64bit computer over firewire to target.
run "C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe" as administrator
Choose File > Kernel Debugging > 1394 > and select channel like on target
and get finally
Using 1394 for debugging
Checking 1394 debug driver version.
Could not find C:\Windows\system32\drivers\1394kdbg.sys.
Attempting 1394 debug driver installation now. "i get pop up to install drivers"
Driver installation successful.
Retrying 1394 channel open.
Opened \.\DBG1394_INSTANCE10
What is interesting when i did install "Windows Drivers Kit 7.1.0"
i didn't found 64bit version of debugger in "C:\WinDDK\7600.16385.1" folder.
Installation of 1394 kernel debugging on Target side for winxp x86:
Open a CMD window
attrib -s -h -r c:\boot.ini
notepad c:\boot.ini
Add these lines:
[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[Operating Systems]multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows" /fastdetect /debug /debugport=1394 /channel=10
Reboot the machine
Installation of 1394 kernel debugging on Target side for Windows Vista up:
Read Here