ShutdownBlockReasonDestroy when real power button down - windows-10

Prevent Shutdown on Windows almost using windows API ShutdownBlockReasonCreate when application received "shutdown signal" ,windows message is 17 (need set AutoEndTasks registry key to 0)
simple test with Notepad,if shutdown from start menu shutdown button,Notepad will prevents it.
but if using real power button,windows can not show any prevent UI.
I tested with my application, "close" messages can received ,but can't show prevent UI.
So this is a windows bug or need some special setting on windows?

at last I found a solution. just need use gpedit.msc Go to “Computer Configuration” >manage template>system>shutdown opption set the only one setting to enable (sorry Chinese literal translation xD)

Related

Blueprism Application Modeller showing Launch instead of Identify when spying

I am using BluePrism v6.1.0 and I am trying to identify elements from a launched application in Application Modeller. (I used the Windows application type in the modeler configuration)
From some tutorials I saw, the launch button changes to Identify button after the app is launched, however, mine is still showing "Launch". Please see screenshot below
screenshot
You need to launch the application from the application modeller, not on your own.
Since you are using Windows 10, the built in applications are use differently than normal in windows 7. Here is how you can add the code to make it work with your system Screenshot. Also for future applications use this code in Windows Power Shell to get information about the application you wanted to work with in Window 10 : "Get-AppxPackage"
Not fully explained here but this can also mean not only is the app not launched but blueprism can't "see" the app is launched. Two ways to solve this so close the application and relaunch it then it will change to identify, OR you can attach the current instance of the object to the running application.
Either way the outcome is you're making blueprism see the active application so it will change the launch to an identify option.
Edit: watch out as well, if you connect your application to blue prism and then detach it blue prism will no longer see the running application hence will revert the identify option into a launch option.

Triggering Network Flyout/Toast UI via command in Windows 10

I'm looking for a way to trigger the WiFi menu shown on the taskbar (typically a black bar with available networks. NOT the Settings app). I've been looking for a command of sorts that could potentially be run through something like a batch file but have come up dry.
I have found lists of commands, like the one below, through which you could open the list of networks in the Settings app but unfortunately that's not what I'm after (I'd like to minimise the menu items an end user has access to):
https://www.neowin.net/news/psa-how-to-open-specific-settings-directly-in-windows-10-from-the-run-command
I also realise this question is similar to this one however the user never got any answers other than a similar list to the one above which they provided themselves. I'm hoping new answers and functionality would be available a year on.
In case Windows handles this differently, I am trying to have the above set up on Windows 10 on a tablet device (Linx 1010).
Any ideas of existing workarounds for this?
EDIT: I've come across suggestions to run "explorer ms-availablenetworks:" (as shown here: https://www.tenforums.com/tutorials/78108-app-commands-list-windows-10-a.html), however this doesn't seem to be working on my machine. Instead I simply get a Windows Store popup saying "You'll need a new app to open this: ms-availablenetworks"
start ms-availablenetworks:
-or-
explorer.exe ms-availablenetworks:
Does work on normally operating good systems... If it doesn't for you something else is wrong or your not using regular windows 10 home/pro/ent
That is a very low end tablet with an Atom 64bit processor that comes with a 32bit OS. I would reinstall Windows 10 64bit on that and everything should work fine afterwards..

How to check what LoadRunner Controller is currently doing?[TruClient]

I have a script which was developed using TruClient for a web application. When I'am going through this test manually everything is working fine. When I'am doing the same test using TruClient in Virtual User Generator everything is fine as well(automated script is written properly).
The problem starts when I'm using LoadRunner Controller. From specified moment all the tests are failed(circa after 40 passed iterations/10 Vusers).
My question is: is there any possibility to check what was wrong on the website? Maybe take some screenshots or something?
(Controller 12.02.0.0 Build 1258)
Not sure if you know about this, but this is where I debug TruClient (and all) scripts which are running in Controller mode.
1) Goto the "Run" tab
2) Double click on the group of the user you want to look at.
3) Right click on the user you want to look at (some could be running or failed)
4) Select "Show User Log"
This will show the console output of the script so will show you then a step starts or finishes, and any LR.log statements you have scripts.
You can enable get screenshots on error (I think it may be enabled by default) in the run-time settings, but I haven't had any luck with the option in there to get a screenshot of every step.
If you restart a user then your logs will be overwritten.

Remote Debugging Azure Worker Role

There are a million links like this one http://blogs.msdn.com/b/cie/archive/2014/01/24/windows-azure-remote-debugging.aspx, which more or less would seem to take care of the remote debugging setup. I have done this many times in VS 2013 Update 2, deployed, then attached to debugger and it simply does not work. Well, the debugger seems to attach, but I continually get the message when I hover over a break point informing me that 'The breakpoint will currently not be hit. No symbols have been loaded for this document' A while back I recall seeing a channel 9 presentation and they seemed to configre the symbol store. I tried configuring this and it still gives me the same message when hovering over the breakpoint.
VS 2013 Update 2 Remote Debugging - I can only get it to work with a 'Debug' build. I have set the Debugging Option "Enable Just My Code" and loaded all symbols -- this seems to work fine. I can now set breakpoints and do not receive the message you (and I) noted earlier.
This is probably not the ideal situation as it would be nice to be able to attach the debugger to a production release but it seems to be a semi-reasonable workaround for now.
EDIT:
Important points:
You must enable Remote Debugging in the Azure Portal for your Cloud Service or Web Site -- Configure Tab (it only remains enabled for 48 Hours)
The debug attribute of the compilation element in your Web.config file must be set to "true". This means, you either have to do a 'Debug' build or manually edit the Web.config file. Here is a link to official Microsoft documentation with a full explanation and a great example of how to do that without redeploying your application:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug
If you still have problems you may have to disable the Debugging Option Enable Just My Code in Visual Studio
I had the same problem - also with VS 2013 Update 2.
The crucial bit I missed was selecting the w3wp.exe process in the pop-up that shows the running processes before hitting the Attach button.

How can I run a performance and diagnostics session on a Surface RT machine?

I am trying to launch a remote performance and diagnostics session on my Surface RT machine in Visual Studio Express 2013 by selecting Debug -> Performance and Diagnostics. However, I get the following message:
Diagnostics session failed to start.
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named '192.168.11.43:4018 (< device name >)'. Connection request was rejected by the remote debugger. Ensure that the remote debugger is running in 'Windows Authentication' mode.
OK, fair enough, so I change the remote debugger to Windows Authentication mode, but no matter what I do I can't authenticate because my PC and tablet are on different domains (that is the way it seems anyway). The tablet is running Windows RT, of course, so it is impossible to change the domain. I have tried to start the remote debugger from the command line using the -u switch with the username and domain from my PC but that was no good either since the tablet can't authenticate it. I also tried to join the tablet's domain on my PC using the script from this answer but I don't get a successful return value (the return value is 5).
Most of the blogs I have come across say "just save yourself the trouble and switch to 'No Authentication' mode" which is what I did in the first place, but the diagnostics session refuses to run this way. What hoops do I have to jump through to get this to work?
Unfortunately I don't think you can get this to work on an RT. Our team has Pros for exactly this reason. Not being able to join a domain is the killer. :(

Resources