We found a pre-release version of Office error - ms-office

I just wiped my machine and did a fresh install of Windows 8 and updated it to Windows 8.1.
I am trying to install Office Professional 2013 and I am getting this error:
We found a pre-release or Beta version of an Office product on your
computer and can't install because of it. Please uninstall any
pre-release Office software using the Programs and features item in
the Control Panel and try installing again.
The thing is, this is the first time I've tried to install office since wiping the hard-drive and re-installing Windows. So there is no Pre-release or Beta version installed. The only software I have installed since the machine was wiped, is Windows, Visual Studio 2012 and Kaspersky Internet security.
I downloaded the Microsoft Fix It tool and it is also throwing an error when I attempt to run it saying
The program encountered an error trying to contact the server
Has anyone encountered this or know how to fix it?

So I got this sorted in the end.
I downloaded the Office FixIt tool which Uninstalled office. I think what happened was the first attempt to install Office failed for some reason, so when I went to re-run it, it thought I had a version already installed.
I deleted the temporary internet files through the Settings, Options, menu in Internet Explorer.
I downloaded the Office click to run.exe again but saved it as a different filename. I just called it office.exe.
Ran the office.exe file I downloaded in Step 3 and it worked, although the installation was very slow.
For some reason my download speeds from Microsoft today seem very slow, not sure if that had something to do with it.
Anyway Office is installed now.

Related

Failed to create imageSource from the text '..\Images\Medium.png

I recently migrated windows 8.1. But unable to open vs2013/vs2012 new Project template.
IT was working fine in windows 8.
ERROR: Failed to create imageSource from the text '..\Images\Medium.png'
Tried all options but did not succeed.
Please HELP
This is because you migrated from windows 8 to windows 8.1
First Go to Control Panel --> Check Updates for Windows 8.1
Install All Important Updates
Restart Your Pc
All things will properly work..
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!
I tried all the steps mentioned above and it did not work. Even I was not able to uninstall VS.
I reapaired .NET framework through Contrl Panel->Programs and Features-> Microsoft .Net Framework-> right click Chane/Uninstall Repair .Net Framework.
This solved the problem.
I got same error after Oracle Data Provider for VS 2013 installation. I installed all Windows 8.1 Important Updates but it didn't work. I read somewhere that it can be happened because of lastly installed VS Add-On etc. then uninstalled Oracle Data Provider for VS 2013 and problem solved.
I am using Visual Studio 2012. This problem occurred to me after I upgraded from Windows 8 to Windows 8.1, so it is definitely related to the OS upgrade.
As some answers say, installing updates for Windows 8.1 will resolve the issue. But you don't need to install everything. I installed only the .NET related updates. Specifically, I installed "Microsoft .NET Framework 4.5.2 for Windows 8.1" (KB2934520), and a few others "Security and Quality Rollup" updates as well.
After a reboot, the "Loading Components" dialog shows up briefly upon launching Visual Studio, indicating that the cache of some components are invalidated and they are compiled again. After that, the "Add Reference" dialog works again.

Visual Studio 2012 Update 4 error

Visual Studio 2012 Update 4 install fails with the below error message, this happens with both the online installer and the ISO, the environment is Windows 7 Enterprise x64 SP1
To solve this problem, do the following before running the update. But if it's already too late, then uninstall the update, then repair the VS2012 install from Add/Remove Programs and follow the below steps (you may need to reboot your computer a few times). More info can be found on this blog (yes blog is for Update 3, but also applies to Update 4)
Download the ISO then run extract the contents and navigate to
"...\packages\WinACK\", and run the below msp patches
Windows App Certification Kit x64-x86_en-us.msp
Windows App Certification Kit Native Components-x64_en-us.msp
Run the update exe "VS2012.4.exe"
Note that this is what worked for me. Would love to hear what others have done to get it to work and share the knowledge especially because I had to struggle because the info was out there in bits and pieces and mostly related to older updates.
I've had other errors relating to the Presentation Framework and the solution for me to was log out of my Domain admin account and log into Windows as a local admin account before installing the update. Not sure if this will work for you too or not, but thought I would mention it.

Remote debugging Tools Cannot Install on Surface RT Running 8.1 Preview (cannot verify digital signature)

I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.

I cannot create a Cloud Project after installing Azure SDK 2.0

I installed the new Azure SDK from the Web Platform Installer.
Now when I try File > New Project > Cloud > Windows Azure Cloud Service > OK
Then I get this error message:
Error: this template attempted to load component assembly 'Microsoft.VisualStudio.CloudService.Wizard, Version=1.0.0.0 ...
I have tried everything I can think of including uninstall of the 1.8 SDK, uninstall of the 2.0 SDK and reninstall. Always I get this message. I cannot see anything about this on the internet. My install gave no error messages.
Also noticed that now in Server Explorer I only have Data Connections, Servers, Windows Azure Service Bus and WIndows Azure Web Sites. There's nothing for storage.
Does anyone have any ideas what may be wrong.
I've had the same problem with skd 2.0
Even trying repairing or installing missing features won't work.
After hours spent on repairing and reinstalling, the only solution I found was to uninstall BOTH Visual Studio and Azure sdk, and installing them again.
After the reinstallation it works fine, but I still have no clue why :P
I keep a development VM for each SDK that comes out. When I upgrade older projects to newer SDKs there are bugs, sometimes bugs without workarounds. I've learned the hard way that installing a new SDK is dangerous.
If you can, develop inside a VM and take occasional snapshots. Otherwise, you do end up reinstalling Visual Studio and installing the original SDK that you first created you project with. -Richard
I've seen this issue on multiple machines after upgrading to 2.7, 2.8, and/or 2.9. Reinstalling VS, VS Updates, and/or SDKs would sometimes help, but sometimes not. The last time no combination of installs worked.
I finally ran Visual Studio with logging enabled via Devenv /log, and according to the %AppData%\Microsoft\VisualStudio\{version#}\ActivityLog.xml file, there was an error merging the configuration file located at %LocalAppData%\Microsoft\VisualStudio\{version#}\devenv.exe.config I deleted that config file and restarted Visual Studio and the problem went away.
Uninstall Visual Studio using VisualStudioUninstaller did the trick for me.
Then I did a clean install of Visual Studio and Azure SDK, and everything worked just fine!

Firebird NET Provider and Visual Studio 2012

I've installed Firebird NETProvider and DDEXProvider on Windows 8 Enterprise (64-bit) with Visual Studio 2012 Premium successfully: I added a connection in Server Explorer and was able to see the database-objects.
However, when I install other extensions (Web Essentials, Power Tools, Resharper) I loose my previously saved connection and I'm unable to re-create it, because the Firebird NETProvider is no longer available. The same result after installing Windows updates (KB2781514), concerning a fix for VS2012.
Re-installing the NETProvider and DDEXProvider causes problems in the VS-configuration (double entries of dataproviders, etc.).
I'm unsure in using the Firebird NETProvider in a project with legacy Firebird-database) , because it seems to be unstable in VS2012.
Hopefully someone can help me.
Many thanks in advance
Dirk Schelfaut
I had the same problems after installing VS 2012 SDK. Solution: Click the Advanced button in the installer and verify whether the correct combination of VS and OS is checked. With my installation, VS 2012 (64 bit OS) was checked, but I had W7 32 bit... You also may have to check the machine.config file. After re-installing, I had several duplicate entries for the Firebird data provider. Regards, Ulli.

Resources