I have a strange problem with my windows 7 (64 bit professional). My compiler output binaries (.exe) files are locked after running. They are locked for about 5 minutes. So I can't compile a new version, I have to wait until it is unlocked. The programm or the debugger are not running (according to the task manager), I used the unlocker (http://www.emptyloop.com/unlocker/) but only got an "access denied". In the Windows Expolorer I can't delete the file, "access denied". I suspected the anti virus programm (Avira Antivir), so I deactivated the realtime scan and added an exception for the output file. No changes.
This happens with different development environments and different compilers:
Qt Creator with MinGW (Qt5)
Qt Creator with MSVC 10 (Qt5)
Sharp Develop with C# .NET 4.5
I hope anyone has an idea why my windows behaves that strange or, even better, how to solve it.
Finally, I found the answer. After I started the "Application Experience Service", the problem was gone.
Related
I am having problem with installing the PE version on a Windows 10 machine. Even if I skip this error, several other errors pop up. Any idea how to proceed?
I have similar problems on client machines. Skipping all errors usually works, actually. In my case, they are caused by the installer trying to copy example models into a part of Windows that is locked.
Skipping still lets me use AnyLogic, just no example models.
See if you can install as an admin (right-click the installer and launch as admin)
We have a VSTO Application that is installed on many machines. If the Add-In is already installed, there is no issue. If you try to uninstall or install, you get the following error message:
The following Microsoft Office solution cannot be installed due to a general installer error: App_Name.vsto
0x80070002
This application has been working without hiccups for almost a year now. Our Sys Admin and I believe we've narrowed it down to a mandatory Windows 10 update as our base Windows 10 image has it working fine and it works on Windows 7 no issue. However, the update is already pushed out and nothing is showing up in the logs.
I know the VSTOInstaller.exe.Config file has been the cause for several of these installer issues, however I cannot find that file on any of our machines even though I KNOW I modified one machine and changed the name to VSTOInstaller.exe.Config.Old for the Business.fba error some have gotten. I assume an update somehow packaged the config file into the .exe.
The Windows 7 machines also don't have the Config file as well...
What we've tried:
Searching for an older .Config file to place in the folder
Rolling back to a previous version
Recompiling
Changing the publish destination folder and setting version back to version 1.0.0.0
Update: Placing a VSTOInstaller.Exe.Config then a VSTOInstaller.Config in the C:\Program Files\Common Files\microsoft shared\VSTO\10.0 folder
Update: Running repair then doing an uninstall/reinstall on Visual Studio Tools for Office Runtime (x64) program from Control Panel.
Update: Cleared Application Event Log
Update: Stopped Windows Update service, Renamed C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistributionOld, then restarted the Windows Update service.
I'm at a loss. Any help is GREATLY appreciated.
If anyone has the VSTOInstaller.exe.Config file, I'd love to try and place that in the folder to see if it works.
Version:
Word Version - 16.0.6769.2040
VS Version - 14.0.25420.1
OS Version - 1511 (OS Build 10586.494)
Turns out the error was part of a Microsoft Office update. Unsure if somehow the update listed in the question updated Office 2016 in the background somewhere.
The steps to resolution were as follows:
Uninstall O365 from the Control Panel
Download the a full removal tool and run it from https://support.office.com/en-us/article/Uninstall-Office-2016-Office-2013-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8
At this point after those have ran, uninstall the add-in if it was installed.
Reinstall O365
Reinstall/Install the VSTO Add-In
Easier resolution than I thought and really appreciate all the assistance.
Windows 10 Update error 0x80070002 or 0x80070003
Step 1: Windows Service Checklist:
Open Windows services.msc, check the following services status (If it is different set it to the recommended settings)
[enter image description here][1]
Disable any third party antivirus applications, as it may block the Windows 10 upgrade process.
Step 2: Reset Windows updates:
Resetting windows updates, in this step we will clean up old failed updates that have been saved in the computer, let start by first disabling the windows update service.
Service Status(Start/Stop/Blank) Automatic/manual/Disabled
Background Intelligent file Transfer Started Automatic
Crytographic Service Started Automatic
DCOM service Started Automatic
RPC Started Automatic
Windows Modules Installer Started Automatic
Windows Update Started Automatic
Windows defender Blank Disabled
Windows firewall Blank Disabled
Disable Windows update service and stop the service
Now open Run command and type %windir%
Check for Software distribution folder delete the folder. (If it fails restart the computer, then try deleting it)
In Run command window type “cleanmgr” to launch disc cleanup to clean old junk files.
Restart the windows update service set it Automatic. Once completed, the windows upgrade error code 80070002 should be resolved. Try the upgrade now. Still unlucky, get in touch with us or proceed to next step
Step 3: Dism/Readiness Tool
This step is to fix core Operating system files that are corrupted and is affecting the Windows 10 upgrade and causing the error. Most of the cases running the tool or the command will fix the corrupted files, there are cases where some stubborn files remain. We can assist you in repairing them manually, post the log to us so we can check and revert back to you.
Depending on the OS, you have to choose proper tools,
For Windows 8 and higher use the following command in elevated command prompt.
Dism /Online /Cleanup-Image /ScanHealth
For windows 7: Download and run windows update readiness tool
microsoft.com/en-in/download/details.aspx?id=20858 –X64
microsoft.com/en-in/download/details.aspx?id=3132 – X86
Check the logs for the above tools in the following location
%windir%/logs/cbs
Post the log for further steps.
Please refer to this link for more info :
http://www.msofficelivesupport.com/windows-update/windows-10-update-error-0x80070002-or-0x80070003/
I have been using some powershell scripts to query active directory users and its very useful
Recently the script stops working even though I have not changed it !
I don't understand why. The prereqs etc. have not been altered
The errors im getting include:
"import-module: a local error has occurred .... { import-module $_ }...
Error initializing default drive: 'a call to SSPI failed see inner exception...
I am using windows 8 64 bit had all the pre reqs sorted e.g. RSAT tools, powershell option enabled. Dot net 4.5 etc. have enabled RSAT through add remove programs.
I have tested the same script on another windows 7 machine and it works fine which makes it look like there is something awry on the windows 8 machine. I have googled about but haven't found a working solution.
Ive checked to see if id unchecked anything that would upset powershell but don't see anything. Ive recreated my windows profile, I have reinstalled the RSAT tools for windows 8.1 64 bit. Ive re domained the machine.
The active directory scripts were running fine then suddenly stopped. I haven't Installed any software recently. I'm a domain admin and can use active directory with the gui with no problems. I'm at a loss.
Wondering if anyone knows what could have upset powershell on the windows 8 system or see anything ive overlooked
Thanks for reading
Confuseis
I tried to install this program that open by windows msi installer and there was problem with a message "Installation incomplete" follow with error message below " The installer was interrupted before FaxFinder Client software could be installed, you need to restart the installer to try again".
This is software for digital fax and we are using the old version, I already been doing this many times already with success installations, if there was a problem, I usually trouble shoot it by restart the windows 7, and log back in with my admin rights.
But this time is different, I have been tried so many times and always showing the error message. On installation progress I saw that all files are installed into a folder, and located on program files (using x64 bit), but when the installation about to finished, I saw Status: Rolling back action, stopping services(I believe it stopped at point print spooler) and ended in result "Installation Incomplete".
I am using windows 7 pro OS and part of admin group in my network. Could somebody help me with this error message please? I appreciate it.
Edit:my questions might be not really clear, ok let me try this again:
when I checked the print spooler from services.msc showing a weird behavior, it stopped, started, and stopped again, I set the start up type to automatic, and I have admin rights on this computer. I also tried to install the program in safe mode, but it won't let me install it. the program itself doesn't have run as admin option.
Thank you for your response. I found out from vendor's website, that saying windows KB3072630 preventing installation, to whoever has the same problem like mine, please check this link, that works only if you installed faxfinder client older version (ff20).
Hope this could help!
first things first:
It was working when I used it last time (which is about more than a month ago).
The Problem is, that no command which is from an extension is working, it seems like no extension is loaded.
Only the default commands do work (like version etc.)
The output of the command "Version" is:
Extension DLL chain:
dbghelp: image 6.2.9200.16384, API 6.1.6, built Sat Nov 20 12:57:48 2010
[path: C:\Windows\system32\dbghelp.dll]
ext: (Not loaded)
wow64exts: (Not loaded)
exts: (Not loaded)
uext: (Not loaded)
ntsdexts: (Not loaded)
It says that no extensions were loaded, but the folder winext does exist in my system32 folder (C:\Windows\System32\winext), where the extensions are located in (as far as I know).
Commands like !gle do not work :/
I really have no Idea what I can do, please help me :)
Does the DBGTOOLS definition in your IDA.CFG point to the x86 WinDBG installation directory?
The following comes from IDA Pro's help:
Windbg debugger plugin has the following configuration options:
- The Debugging Tools folder: This should be configured to point to the same
folder where Microsoft Debugging Tools are installed. The plugin will try to
guess where the tools are, but if it fails, a manual intervention will be
required. If this option is not set, then the plugin will try to use dbgeng.dll
from MS Windows system folder, while normal debug operations will work,
extensions will not.
This information indicates that if IDA Pro is using dbgeng.dll from the Windows system folder, the extensions command (like !gle) will not work.
If you have already setup the DBGTOOLS to point to your WinDbg (x86 version) directory correctly in your /cfg/ida.cfg but IDA Pro is still using dbgeng.dll from your Windows system folder, then probably your IDA context is not configured to analyze the IBM PC processor. This may happen when you launch IDA Pro and click the 'Go' button directly to work on your own and start the WinDbg debugger.
Check the DBGTOOLS in the ida.cfg, you will find it is wrapped by #ifdef __PC__ #endif.
The __PC__ will only gets defined by IDA Pro if you are analyzing a Windows EXE file for example. Give a try to launch the WinDbg from the IDA Pro menu after you have successfully disassembled a Windows EXE file and see what happens.
If this still hasn't been answered your problem is most likely that you didn't uncomment the DBG Tools line in the ida.cfg file.
I just fixed this myself. hope this helps.
Also the other guys are correct as well. make sure you are escaping with double back slashes "\\" and make sure you pointing to the (x86) directory.