Swivel is a free swf to video converter made by Newgrounds with the needs of flash artists in mind, but i havent used it much yet so i'll let this guy explain. So far the best thing about it i have noticed, is that it allows you to convert multiple swfs into one video file back to back. But now we have Swivel. Swf converter. Which I would imagine would make compiling a collab rather easy.
Please wait while windows configures microsoft office enterprise 2007 and it takes about 6 mins to launch the app and it does this everytime i launch it. If every time you open Microsoft Office 2010 you receive the following message: Please wait while Windows configures Microsoft Office, see this.
Running under WIN7-64 bit with Office 2013. Requests reinstall every time it is run. Tried uninstalling and reinstalling. Office 2013 does not recognize that Visio 2007 is installed.
Copy paste operations between Visio and Word 2013 don't work. Tried disabling sharepoint access for Visio 2007 and did a repair for Office 2013. No change.Tried various compatibility modes. Ran Microsoft troubleshooter which verified there is a compatibility issue but provided no solution. Tried the following. Type the following command, and then press Enter: reg add HKCU Software Microsoft Office 14.0 Visio Options /v NoReReg /t REGDWORD /d 1 no change.
Hi, In regarding to your description, my understanding it that Visio 2007 could not work fine with Office 2013. If you start the Visio 2007,you got the error message 'Please wait while Windows configures Microsoft Visio'.For it, there is a Kb explaned it: You'd better upgrade the Visio 2007 to sp3. Then fix it and test again. Here is an article to introduce the compatibility of Office 2013: I recommend we could use the same version to work together and it'll avoid some unexpected issue.
Regards, George Zhao TechNet Community Support. Same problem here. We are moving from Office 2007 ProPlus to Office 2013 ProPlus. We uninstall the old version of Office but keeping Visio and Project 2007.
Once Office 2013 has been installed, every time we start Visio 2007 it gives the 'Please wait while Windows configures Microsoft Visio' message. Project 2007 works fine.
I have tried the suggestion above, I have tried to re-register Visio manually with the /r option, I have tried Office repair. Nothing worked. I have checked that the.vsd extension points to Visio.Drawing.11 and it does. The only way to not show the message is to run Visio with the parameter /noreg which is not an option for us. I have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a.vsd drawing file or the VISIO.EXE.
I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped. However the Windows Update titled '2007 Office System Update' KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now SOLVED. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a.vsd.vst or the VISIO.EXE, including the desktop shortcut.
See the article below for a detailed description of this update. DO NOT INSTALL. Try uninstalling this update: KB2767916 'Update for Microsoft Office 2007 suites' Windows Update - Installed Updates - Select this item - Uninstall. For me, this magically fixed the problem with Visio 2007 and Visio 2013 install on the same machine (and Visio 2007 crashing or constantly reinstalling). Nikolay Belyh, visio.com I know this is an antiquated thread (issue), but the fix is still valid.
Thank you, Nikolay Belyh! Not only did this fix the constant reinstalling of Visio 2007 when opening issue, but it also fixed an issue I had where I had to save the file(s) I were working on, with a new name, every time.
I was happy when I found the KB2767916 'Update for Microsoft Office 2007 suites' figuring it would work for me as well. Unfortunately, uninstalling the KB did not work for me.
I still get the 'Preparing to install.' Followed by 'Please wait while Windows configures Microsoft Office Visio Professional 2007' before the program finally opens. I then tried the: reg add HKCU Software Microsoft Office 12.0 Visio Options /v NoReReg /t REGDWORD /d 1 as well as the other suggestions above and still no success.
I will keep searching and post back when I find another answer that may help others.
Visio 2013 startup problem 'Please wait while Windows configures Microsoft Visio.' I am running Win 7/Office 2010 and I've installed Visio Pro 2013 on 3 machines (manually and deployments). Once install is complete, when you open Visio Pro the windows configures each time.
I've tried the following 2 steps and no success. Reg add HKCU Software Microsoft Office 15.0 Visio Options /v NoReReg /t REGDWORD /d 1 To manually fix this issue, run 'regedit' and manually change the value of HKEYCLASSESROOT.vsd to Visio.Drawing.11 (if using the Visio client) or VisioViewer.Viewer (if using the Visio Viewer). Thanks for the assistance. I was able to install Visio Pro 2013 and open up without configuring on 1 of the machines.
I tried 2 things one of which may have worked. Your suggestion above on the update allowed me to remove another update KB259981 Visio Viewer Update Describes a vulnerability in Microsoft Visio 2010 Viewer could allow remote code execution. I also installed Project Std 2013. Project Std installed and opened up without the configuration start up issue. Installing Project Std also included the additional install of the Office 2013 Language Preference program. I suspect this had an impact on the installation of Visio.
I'm wondering if during the install start up issue that the program was configuring the language preference for Visio. I made both changes at the same time so I can't confirm which worked, just glad that issue resolved. Hi, 1.Please try to click Start click Runtype the following command press Enter: secedit /configure /cfg%windir% inf defltbase.inf /db defltbase.sdb /verbose See if the problem has been solved. 2.If this problem persists, try to start Visio in safe mode, if the problem does not occur in the safe mode, this issue might be related to some third-party add-ins in the Office program, you can try to disable them.
Normally, you could do the following to disable the conflict add-ins in your Office program. 3.if the problem still persists you can visit, download Fix it 50780 and use it to fix the problem. If all fails, well, uninstalling Office completely and re-installing it. Regards, George Zhao TechNet Community Support. Thanks for the assistance.
I was able to install Visio Pro 2013 and open up without configuring on 1 of the machines. I tried 2 things one of which may have worked. Your suggestion above on the update allowed me to remove another update KB259981 Visio Viewer Update Describes a vulnerability in Microsoft Visio 2010 Viewer could allow remote code execution.
I also installed Project Std 2013. Project Std installed and opened up without the configuration start up issue. Installing Project Std also included the additional install of the Office 2013 Language Preference program. I suspect this had an impact on the installation of Visio. I'm wondering if during the install start up issue that the program was configuring the language preference for Visio.
I made both changes at the same time so I can't confirm which worked, just glad that issue resolved. Visio 2013 on 2012 r2 terminal server had the same issue. This issue seems to have been in every version of visio while the fix varies on version. So the problem seems to come with visio wanting to register the file associations on launch, this causes a msi repair. Unfortunately the msi repair does not fix the key, nor does uninstalling and re-installing update the key to the correct value. Because hkeyclassesroot is a combination of the users file associations hkeycurrentuser software Classes (this is where the bad key exists) and hkeylocalmachine Software Classes You will notice the key.vsdx exists in both locations, the HKLM value for me was actually correct. The problem is that hkeyclassesroot is actually the net result of hkeylocalmachine Software Classes and hkeycurrentuser software Classes, where hkeycurrentuser software Classes is always the winning key.
So the visio on launch detects that the file association for.vsdx is incorrect and tries to correct it with a repair, but the repair does not update they key for hkeycurrentuser software Classes.vsdx that is actually causing the issue. The net result is that visio repairs on every launch but never fixes the problem. Anyways that's the problem and the reason behind it, the fix is below. As a test I ran visio.exe with the switch /noreg 'C: Program Files (x86) Microsoft Office Office15 visio.exe /noreg' and it started without re-installing. I found a heap of people with this issue, one of the fixes for older versions of visio was to update hkeyclassesroot.vsd (default with Visio.Drawing.15) Visio 2013 saves files as.vsdx, this led me to hkeyclassesroot.vsdx I noticed this set to the wrong value of 'vsdxautofile' Using preferential policy because we needed a solution for new users, I set it to update this key to the correct value. I verified the key does not actually exist in the default user profile, so you cant fix it there.
The only way I found to fix it long term for all users was to use a policy to update the key for all users when they log on. 'hkcu software Classes.vsdx' the default value should be 'Visio.Drawing.15' Here is a copy of the preferential user policy, if you are running an enterprise with AD and Group policy you can use the following to update the keys. So the log of the short is verify the following keys are set to 'Visio.Drawing.15' Open Regedit.exe Update these keys HKEYCLASSESROOT.vsd and HKEYCLASSESROOT.vsdx to the following The (default) value should be 'Visio.Drawing.15' or run visio.exe with the /noreg switch, the only problem with this method is that running a shortcut with the switch does not solve the issue for people that double click a.vsd or.vsdx file directly. I lost a day and a half on this, it seems the problem dates back to nearly every version of visio.
I would be good if MS developed a long term fix.