I do have the steps, my Windows is in french but I can deduce what to click. It's just that I need more exact steps to guess better the translation and the idea:
Open Search Windows
What program to type ?
What to click in the program to see and change users ?
There are two scheduled tasks un Task Scheduler
Quoted from Costas2 in April 2017,
Library/Microsoft/Office:
OfficeBackgroundTaskHandlerLogon that runs when a user logs on and
OfficeBackgroundTaskHandlerRegistration that runs every hour
Both were set to run under the "Users" account group. Since I didn't
notice any popup at logon, I set
OfficeBackgroundTaskHandlerRegistration to run under the "System"
account and the hourly popups are now hidden. (Select the task, right
click, Properties, click on 'Change User Or Group', type 'System', OK
twice and voila.)
This is not the best solution from a security point of view, but until
MS fixes it, it works for me.
It's mostly for me to understand how to fix the Windows bugs without saying nonesense all the time, and in case there are other terminal windows types that opens all the time later. Windows said it already sent the fix to the bug: " The fix is now available in mainstream builds 16.8210.2075 released on 6/6/17 " So we don't need to do nothing, just wait. It's just that I was beginning to understand informatics and now I'm totally lost, I have no idea where to begin, neither how to follow the steps quoted.
Quote is from here:
OfficeBackgroundTaskHandlerRegistration flashes a window every hour (Microsoft Answers, 2017)
Update Microsoft Office. Open any Office 2016 app and choose:
File > Account > Update Options > Update
Source
Thanks for the answer: Fichier > Compte > Mises à jour pour Office (fr)
Although I won't do it, I found that on the net today, seems like it answers my question, just a quote found:
Kevin Angus replied to Steel Horn
05-31-2017 06:24 AM Re: OfficeBackgroundTaskHandlerRegistration
comman...
Open a DOS window enter Taskschd.msc OR open Control
Panel/Administrative Tools/Task Scheduler
Click to the left of Task Scheduler Library on the >
Click to the left of Microsoft on the >
Click on the Office folder
Click on the forth (4th) item down below Name in the center of the
window
Verify it is OfficeBackgroundTaskHandlerRegistration
Double Click the forth (4th) item to open the edit window
In Security options
Click on Change User or Group...
In the Enter the object name to select box enter system and click
Check Names
Click OK
Click OK
Quote found here: Microsoft's Techcommunity
Related
Every time I launch the native Figma app on macOS (macOS 13 Ventura) I get this notification:
Login Item Added: "FigmaAgent.app" will open automatically when you log in. You can manage this in Login Items Settings.
And following the instructions on the notification I can remove the Login Item as expected, but I will get the notification again next time I launch the app, and the Login Item will be added once more.
I want to remove it and never to be added again.
How can I do that?
Pd: I reached out to Figma support a few times, and they mostly ignored my messages, and when I asked why was I being ignored they gave me a rather unhelpful answer:
Hey there, sorry for the delay & confusion. We didn't reply, because the answer was in your original tweet. Sorry if it wasn't obvious, but in the screenshot, you manage it from Login Items Settings: Apple menu > System Settings, click General in the sidebar, then Login Items.
To be very clear, I don't want to know how to remove FigmaAgent from Login Items, I want to know how to prevent it for being added again.
From https://twitter.com/qdoug/status/1374785043504185351:
This seems to work for removing FigmaAgent:
Force Quit it in Activity Monitor
Remove it in System Preferences -> Users & Groups -> Login Items
Delete ~/Library/Application Support/Figma/FigmaAgent.app
Delete /Applications/Figma.app/Contents/Library/FigmaAgent.app
I have an issue with an auto start of Outlook 2016 at boot/log on which is intended to start Outlook minimised to the Windows system tray, such that once invoked at Windows 10 launch mail will be collected by the mail account(s) (NB. All POP in this case.) whilst the program resides in the system tray remaining invisible until required by the user.
The .vbs script below does function as required but much of the time it introduces two unwelcome issues.
The Outlook icon in the System Tray displays a 'cog' overlay with the message "Another program is using Outlook. To disconnect programs and exit Outlook, click the Outlook icon and then click Exit Now".
Attempts to open Outlook from the 'Open Outlook' context menu (right click Outlook icon in the tray) item causes a dialogue box to appear reporting "No active explorer object found". Clicking the "OK" option in response launches Outlook (though issue 1 - cog overlay) remains.
Neither issue is present when Outlook is started normally from the desktop so it would appear that the .vbs script is in someway responsible. I have used this script successfully (see also below: https://superuser.com/questions/467809/start-outlook-automatically-in-tray) in the past both as a startup menu shortcut and a hkcu 'run' registry entry.
Can anyone suggest the cause or alternately a suitable code revision to achieve correct function? In case it is significant, Windows 10 is 64 bit Pro and the version of Office (including Outlook) installed is also 64 bit.
This is the code invoked by the .vbs script:
OPTION EXPLICIT
OPTION EXPLICIT
CONST PATH_TO_OUTLOOK = """C:\Program Files\Microsoft Office\Office16\OUTLOOK.EXE"""
CONST SHOW_MAXIMIZED = 3
CONST MINIMIZE = 1
DIM shell, outlook
SET shell = WScript.CreateObject("WScript.Shell")
' Open Outlook
shell.Run PATH_TO_OUTLOOK, SHOW_MAXIMIZED, FALSE
ON ERROR RESUME NEXT
' Grab a handle to the Outlook Application and minimize
SET outlook = WScript.CreateObject("Outlook.Application")
WScript.Sleep(100)
outlook.ActiveExplorer.WindowState = SHOW_MAXIMIZED
' Loop on error to account for slow startup in which case the
' process and/or the main Outlook window is not available
WHILE Err.Number <> 0
Err.Clear
WScript.Sleep(100)
SET outlook = NOTHING
SET outlook = WScript.CreateObject("Outlook.Application")
outlook.ActiveExplorer.WindowState = MINIMIZE
WEND
ON ERROR GOTO 0
SET outlook = NOTHING
SET shell = NOTHING
Having spent a number of hours on this issue over the weekend I thought that I had resolved the issues and got everything functioning as intended.
Working from similar samples of code I compiled a new script (see below) which I applied both as a shortcut in the Startup folder and also as an entry into the 'run' branch of the HKCU registry.
Now for the issue! Testing the script on two separate Windows 10 Pro (both 64 Bit architecture) systems both with Outlook 2016 64 Bit installed as part of a 64 Bit Office suite I found that whereas on one system the script runs flawlessly on the other I receive the following runtime error:
Script: D:\Neil's Files\Neil's Filing Cabinet\Neil's Emails\Start Outlook Minimised to Tray\Start Outlook 2016 Minimised To Tray.vbs
Line: 11
Char: 5
Error: ActiveX component can't create object: 'GetObject'
Code: 800A01AD
Source: Microsoft VBScript runtime error
This has me perplexed as the script file and it's related shortcut are both physical copies of each other given that the revised script below contains no path references (as these are handled directly by the code in respect of Outlook.exe) which are identified by the placement of either the shortcut or as the data element of the registry string whichever format is used.
The Systems do have some differences however and for comparative purposes I will summarise those I feel to be relevant here:
System 1: (The problem system) is an X58 Asus P6T7, Intel i720 mature PC with many programs installed and specifically the Outlook 2016 has the same 12 addins installed but in addition has two related programs which launch at boot, the enterprise editions of 4team's Sync2 for Microsoft Outlook and Safe PST Backup. The boot times are quite lengthy (but acceptable) as is the Outlook Startup with it's various addins.
System 2: Is a current generation Asus X99-Deluxe, i7 5930 new build pc with little installed as yet save MS Office, Adobe CC and some utilities.
In the case of System 1, Outlook auto-starts as intended however during it's loading splash screen (whilst it is loading up the addins) the runtime error is displayed although Outlook continues to open fully but fails to minimise.....
This suggests to me that the faulting code is the section which activates the window however the above error message refers to "ActiveX component can't create object: 'GetObject'" which suggests instead an issue with the code line "Set OLObj = GetObject("","Outlook.Application")"??
Hopefully somebody can test the code on a similar setup and report back? Or alternately, give me a pointer as to what is going on and how I might resolve it. I would of course also welcome any suggested improvements to the code!
** Quick Update ** Now tested on HP Elitebook 8440P Laptop - Windows 10 Pro 64 Bit with Office 64 Bit + same 12 Outlook Addons - Functions as intended.....
** Further Update ** Tested on a second HP Elitebook 8440P Laptop - Windows 10 Pro 64 Bit with Office 64 Bit + same 12 Outlook Addons - Above RunTime error experienced once again.......struggling to comprehend why these results are occurring?? Any thoughts anybody???
The code below is offered "as is" for the benefit of anyone else seeking the same Outlook auto start criteria. The testing with System 2 indicates that it works so I hope others enjoy similar success until the outstanding issues are sorted.
NB: To adjust the Outlook Launch Window Size (during its 10 second pause prior to automated minimising) to reflect personal preferences change the numeric value in the following line of code:
WshShell.Run "OUTLOOK.EXE" , 3, false
For a maximised window size change the value to 3 For a restored window size change the value to 2
OPTION EXPLICIT
Dim WshShell
Dim OLObj
Set WshShell = WScript. CreateObject ( "Wscript.Shell" )
'Open Outlook: Note that inspite of the launch options, it will open the program in a normal window.
'The file location path is not necessary as Windows 10 correctly identifies Outlook's location.
WshShell.Run "OUTLOOK.EXE" , 3, false
'This will mimimise it to the system tray after a 10 second pause to allow for mail collection on Outlook launch.
WScript.Sleep (10000)
Set OLObj = GetObject("","Outlook.Application")
'Activates the window
OLObj.ActiveExplorer.Activate
'Sends the command to minimise
OLObj.ActiveExplorer.WindowState = 1
'Outlook does not immediately minimise to the system tray so that 'Send/Receive' can initiate mail collection.
Thanks to jrv from Microsoft's "The Scripting Guys" forum who kindly offered a revised (simplified) code which is below. I can report that as with the original code it works flawlessly on the same 2 systems as before, whilst faulting once more on the other two......very much perplexed!!
The Runtime Error:
Script: D:\Neil's Files\Neil's Filing Cabinet\Neil's Emails\Start Outlook Minimised to Tray\Start Outlook 2016 Minimised To Tray.vbs
Line: 3
Char: 5
Error: ActiveX component can't create object: 'Outlook.Application'
Code: 800A01AD
Source: Microsoft VBScript runtime error
The revised code:
Set WshShell = CreateObject ( "Wscript.Shell" )
WshShell.Run "OUTLOOK.EXE" , 3, False
Set ol = CreateObject("Outlook.Application")
ol.ActiveExplorer.Activate
ol.ActiveExplorer.WindowState = 1
You can use like file *.reg:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"Outlook"="C:\\Windows\\system32\\cmd.exe /c \"start \"\" /min \"C:\\Program Files\\Microsoft Office\\Office16\\OUTLOOK.EXE\"\""
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences]
"MinToTray"=dword:00000001
I have an answer that works well with Office 2013 on Windows 7, and I hope it works for you too.
Essentially, this solution bypasses the issue with trying to force Outlook to minimize after loading. Instead, it relies on using a shortcut that's already configured to load the program in a minimized state.
Copy a shortcut to Outlook into the directory containing your script.
Right click the shortcut and open Properties.
In the Shortcut tab, change the Run mode to Minimized. Press OK.
Then, all you need to do in your VBScript file is to execute the shortcut like so:
Dim sh : Set sh = CreateObject("WScript.Shell")
sh.run "Outlook.lnk"
Note that because this solution uses a shortcut, you could potentially remove the VBScript part entirely by putting the shortcut into the All Users Startup folder.
It's me again! I have an answer that should bypass any issues with VBScript by using third-party software, DisplayFusion. I don't know how you'll feel about that, but I tested it and it works over here. I use this at home and at work to manage multiple monitors and various other things. It may even help solve problems with other programs you use and render various VBS hacks redundant.
In your case, there is a feature called 'Triggers'. Note that while there is a free version of DF, you'll have to activate a 30 day trial for the Pro version to use Triggers, and after that, it's up to you to decide if it's worth your while.
Firstly, after installing DF, you'll want to open up its settings window (right-click desktop and go to DisplayFusion > Settings).
Go to the Triggers tab and click Add.
Set up the trigger for when a window is created. Tell the trigger to activate only once per process ID so it won't also try to minimize subsequent windows, such as when composing a new email. Find the path to your outlook.exe. Then, add an action on the right-hand side to minimize the window.
Click OK twice and then see if it works by loading Outlook. For me, the splash screen appears as normal, then the main window is minimized as soon as it appears.
DF runs as a system service with admin privileges and has been tested with tonnes of software packages, so if this method also fails for you, it could indicate bigger issues with your system/Office configuration.
I signed up for a (free) c9 account; verified email address etc.
I selected CREATE NEW WORKSPACE and selected "Ruby on Rails", "Private to the people I invite" (I'm under the impression I get one free Private workspace?), name it "tPRoRD" (abbreviation of the course I'm taking), and select "CREATE"
Expected Behavior:
I hoped to see in the left "MY PROJECTS" pane, adjacent to the default "demo-project", a new project entitled "tPRoRD".
Observed Behavior:
There is a new 'Open and Discoverable' project entitled "tprord"; and a 'greyed-out' project entitled "tPRoRD" which is listed as 'processing'.
When "tPRoRD" is selected, the expected "Start Editing" button is replaced with one entitled "Cancel creation".
I have posted this question on cloud9ide.zendesk.com and have started going back and forth with support - long lags due to time zones.
Has anyone else seen this?
tks! -rb
(may be) SOLVED: appears to be fixed on it's own - does anyone know, the little 'lock' icon next to a workspace name indicate the workspace is 'private' vs 'open and discoverable'?
tks Brady (at cloud 9) and Ruby on Rails instructor Mashrur Hossain for looking into this for me :-)
I initially installed the Microsoft Visual Studio Express 2013 for Web on my desktop. My desktop runs Windows 8.1 with internet explorer 11. It ran fine until the license expired after the first 30 days. I tried to sign in to renew the license, however after clicking the 'sign in' button I get an error dialog. The dialog states 'Browser is security restricted or javaScript is disabled. I have no other option but to close and exit Visual Studio.
I went to the online forums for Microsoft. There were discussions and suggestions on how to fix the error. I tried lowering the settings for the security tab in internet explorer. I have validated the option for scripting is enabled. I have also added https://*.visualstudio.com to the trusted sites tab. Other users on the forum have tried the same suggestions and have not succeeded in signing into the visual studio application.
I had exactly the same problem, here is what I did:
a) Go in IE, click on settings wheel then Internet Options and Security tab.
b) Click on Custom level button (make sure you select Internet zone).
c) In Security Settings window, under Scripting I set Enabled for Active scripting.
After that Sign In should work. Even though Chrome is default browser, it seems that VS uses IE for sign in process.
Hope this helps!
There is another issue people are running into that is a bug with the login dialog. The login dialog is using a Web Browser control to login the user. By default it loads up "about:blank" as the URI. It then proceeds to try to execute some JavaScript (just ";") to verify it has permissions to do so. On some machines this is problematic because "about:blank" has been mapped to zone 0, or the Local Machine zone. When the JavaScript is executed MSHTML will check the zone of the URI and then the policy for executing scripts. By default the Local Machine zone is locked down, and all script executions result in a Query policy. What this means is if you're running in immersion mode (aka in Internet Explorer) you will get a message box asking if you want to execute the script. However, the Web Browser control used by VS 2013's "Sign In" dialog doesn't run MSHTML code in immersion mode, so the Query policy effectively equates to a Disallow policy. The bug here is someone in VS assumed "about:blank" resolves to the Internet zone, and when it resolves to the Local Computer zone you get this behavior.
The workaround is to remove "about:blank" zone mapping. Point regedit to this key:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains]
Remove the "blank" key.
Alternatively you can change the Local Machine Lockdown policy for executing scripts. The reg key for that is:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Lockdown_Zones\0]
Set the "1400" DWORD value to 0.
There are many sites you need to list in your Trusted Sites. Following the trace of what the stupid, stupid login script does:
https://.visualstudio.com
https://app.vssps.visualstudio.com
https://.accesscontrol.windows.net
https://auth.gfx.ms
https://login.live.com
Only then was I able to log on to my FREE software.
Hi this is Albert from Microsoft. Just want to let you all know that this issue has been fixed in the upcoming Update 2 for Visual Studio 2013. Thanks for your patience while we figured this one out :)
Same problem "Browser is security restricted or JavaScript is disabled" here but the solution from #jic didn't work for me..
If you can and it is convenient for you this is a solution which worked for me:
I have created a new user/profile on my PC and for this user it was just working fine.
Before this action I have tried to make an user account which had this problem as:
Power user - didn't work
Administrator - didn't work as well
So the last solution in my case was a brand new user on the PC..
Here's what worked for me.
Open Control Panel, Internet Options.
First, I clicked the Security tab and turned security the security for the Internet zone to its minimum.
Next, click the Privacy tab, then click Advanced. Choose "Accept" for both types of cookies.
Of course you can change these all back after extending your VS trial.
you must change secure settings of iexplore for admin account. If logon by other account, you must start iexplore under admin account or logon under admin account, because you will get license after admin account.
Click on Start --> Run --> type cmd and click on OK.
Command Prompt will be opened. Then enter this command.
ipconfig /flushdns
and press Enter.
Now try to access https://app.vssps.visualstudio.com/Profile/View
It worked for me...
As I can not add a comment yet to the answer of CBGraham, I've to add this note over here:
The solution described from CBGraham worked for me (Thanks Graham). I had to add an additional link:
https://account.live.com
Then I opened the IE and tried to login to a Microsoft site. I left the IE window open and just clicked once again on the VS to login. Then it worked for me. Even with strong restrictions on the IE settings. While I'm surprised why someone should set down his security settings, just to register VS.
I had downloaded and installed VS 2010 Ultimate evaluation for 30 days. It allows me to get a 60-day extension if I register. My register just ended.
2 days ago, I got the extension key by registering but did not enter it because I thought I should wait till the product evaluation period expires.
Now, when I open up VS 2010, it gives me a dialog box with only two buttons:
a) Learn more about upgrading. This takes me to the same page that allows me either to buy or generate an extension key.
b) Close. This closes VS 2010.
How do I enter in the extension key now?
In order to update the product key you need to be logged on with administrator privileges. Try logging on as an admin and the go to the control panel > uninstall/change a program > Enter the product key > click "upgrade."
Here is a link from MSDN on how to do it for VS 2008 trial editions. It is the same for VS 2010:
http://msdn.microsoft.com/en-us/library/cc442563(v=vs.90).aspx
I did the same exact thing and it looks like the only option I could find after tons of googling is redownloading and installing the latest version to use your new key with. Here is the page I found with links to the downloads:
http://msdn.microsoft.com/en-us/vstudio/bb984878.aspx
NOTE: I have not yet downloaded this and tried the key I received from the 60 day extension but will let you know if this works when I get a chance to DL it in the next couple days unless anyone else can confirm.
(Probably too late, but here's an idea that may help someone...)
Try setting your computer's date back to a point in time when your trial was valid (e.g. 1 month ago). I've just tried this on an expired 2010RC and it ran happily, allowing access to the Help>Register menu option.
Of course, attempting to register in this way may detect that you're running "in the past" and refuse (at which point, try setting the clock back and see if it'll let you retry) - but it's worth a try before going through the pain of reinstalling the whole thing from scratch.
Try "Help -> Register Product". It can be your answer