Share panel freezes after win10 upgrade, all versions

[Davidk]

I've just done (5 days ago) an in-place upgrade of my main PC from win7 to win10. Whilst all versions of VS installed open to the main UI Ok, selecting the share panel thereafter (with a vsp loaded, or not - as in wanting to use the DVD burn panel to create a label) causes the program to freeze with the panel outlined but there is no data in any of the share panes (see screenshot), the activity circle is rotating and blinking (like it stopped and started again) every few seconds; mouse movement available but there's no reaction to close, change mode etc, needs task manager to cancel.
Every version installed affected the same way.

Screenshot

Any ideas what causes this, and is there a fix???

[Davidk]

Update
It's more than just the share panel. Parts of the program work - to create a vsp I can import photos, record voiceover, open a vsp in the file list, drag n drop a clip from the gallery and play it, and insert text to a project file. What isn't working - in addition to share - is import video files. Altho this seems a bit flaky - initially, for a clean vsp it failed, but sometimes (once in a dozen or so times on test) importing a clip to an existing vsp works. Mystified, I am.
OTOH, a limited version of the program installed totally under win10 - works fine in all the simple tests I have done for a comparison.

So, suspecting the change of OS mightily, but the evidence suggests that the OS change influence is buried in VS. All but one VS version now installed was installed under windows 7. The MS upgrade process identified those apps and after the upgrade starting them under win10 worked straight off, but doing some work with them - that's the part that's isn't working very well, and I suspect the cause is a VS component expecting a win7 response from the OS and not getting it.

I did an in-place upgrade because I really did not want to have to re-install and configure a bunch of apps, and in the main that's worked. VS is the problem child at the moment and I suspect I'll have to uninstall every version and then re-install each one under win10 - ironic, because that's what I wanted to avoid.

[BJC]

I did just that a couple of years back when the upgrade to Win10 was free - all versions I had on this computer then - and added since - work without any problems (other than the strange idiosyncrasies of VS2019)

but I do wonder if your problems are due to your practice of personalising the installation instead of just letting the installer put them where the developers wanted them - maybe some of your old folders are not in the same place in W10 as they were in W7 you may need to check out all your personal folders

[Davidk]

I've checked that out - all the apps are where there were, and the desktop icons point to them. As I said starting the apps from those icons to get to the user interface isn't a problem: it's what happens after that when using features of the UI (for the moment, the ones that are broken are share - everything in it, and importing video clips. I've no doubt that there are more I haven't stumbled over yet). On the face of it, because that involves an interaction with windows/explorer, that may be where one issue involving the OS is. However, the very same thing works fine when importing a photo image. Bottom line, bits work and other bits don't and the only common denominator is the windows 10 upgrade.

As to my practice of custom installs - no one ever (ever) keeps every item in the top drawer of a multi-drawer filing cabinet - which is what the drives of a computer are. Having information organised and spread over several drawers has always had advantages, and I try to make best use of them.

[BJC]

As to my practice of custom installs - no one ever (ever) keeps every item in the top drawer of a multi-drawer filing cabinet - which is what the drives of a computer are. Having information organised and spread over several drawers has always had advantages, and I try to make best use of them.

yes but does Win10 know about your bottom draws

[gewb]

Latest video drivers for you:

https://downloadcenter.intel.com/downlo ... ows-15-40-

[tletter]

I did an in-place upgrade ... VS is the problem child at the moment and I suspect I'll have to uninstall every version and then re-install each one under win10 - ironic, because that's what I wanted to avoid.

I've done in-place upgrades of Win10 over top of Win7 on several machines running all versions of VS X5 to VS2018 and not experienced this issue so it's not inevitable. However as such an upgrade is significant, some percentage of systems will experience hiccups as they don't all have the same starting point.

I suspect I'll have to uninstall every version and then re-install each one under win10 - ironic, because that's what I wanted to avoid.

You could try running VS in Compatibility Mode in Windows 10.

tletter
https://www.youtube.com/user/tletter

[Davidk]

Compatibility mode for win 7 was tried for the main application executable (vstudio.exe), made no difference. I think that compatibility mainly applies to what the OS is doing to open a app, and in the past generally my experience is that there's only been the one main exe file involved. My Office 2000 may be an exception, but that's a microsoft product in any event. In this case, with VS at least, compatibility isn't apparently applicable to everything an app does once the OS has opened it. And applying compatibility to every file in the installed folder would be - exhausting.

[RobertOZ]

David,
Before you installed Win10, did you run a Windows compatibility test, to ensure your system is suitable for Win 10, my Win7 system is a bit older than yours, but too many components are not Win 10 compatible, making a new system the most cost effective alternative, so will retain Win 7 for the time being

[Davidk]

Robert,
Oh yes, I spent months researching it with Microsoft Answers and Gigabyte. The motherboard manufacturer has win10 drivers for it, and said in passing that these should be part of the win10 package by now. And there is a microsoft upgrade guide available on-the-net. One of it's passing advisories is that an in-place upgrade can only be done from within a running windows session: just doing the upgrade from a booted usb or DVD will give a clean install, meaning everything you wanted to keep - will be over-writtten and have to re-installed and configured all over again. Advice on an upgrade from another source is to un-install any AV suite and re-install after upgrade is complete.

I nearly squibbed upgrade several times in the face of remarks like these. But pressed on: I did all those things and the actual upgrade ran smoothly, no hick-ups or error messages. At the time, a pleasant surprise. And the very first thing I did was to check the software on the desktop - Corel especially - was openable. And it was: not one broke trying to open. It wasn't until nearly a week later that I opened VS to do some last minute work (time critical) on a project and found that the part I wanted to use (share) just wasn't workable on 2019 or any other of the 4 installed (under win7) versions. Reverted to my class laptop for the time-critical work and went back to diagnosing the desktop issues later.

Get More packages
At the moment, every installed (under win7) released version of VS (4) is openable but in practice, unusable. Now that it seems I'll have to un-install and re-install all the VS programs, I'm checking that all the parts I want for that process are accessible on the upgraded platform. And one item I cannot find are the 'free' packages from Get More about menu themes etc which I have downloaded in the past. I am convinced they were saved into the C drive somewhere by default, but cannot find them in the win10 C; Any suggestions about what folder they may be in would be helpful.

[asik1]

David, in your situation what "get more" you need? take it a step up to clean and lean stuff.
I recently deleted scorefitter ~600MB of sounds from VS2018 as I will never use it there.
You better keep only one VS up in full and lean all the others.
It's a pity you didn't image your system before the 10 move.

[lata]

Get More packages
At the moment, every installed (under win7) released version of VS (4) is openable but in practice, unusable. Now that it seems I'll have to un-install and re-install all the VS programs, I'm checking that all the parts I want for that process are accessible on the upgraded platform. And one item I cannot find are the 'free' packages from Get More about menu themes etc which I have downloaded in the past. I am convinced they were saved into the C drive somewhere by default, but cannot find them in the win10 C; Any suggestions about what folder they may be in would be helpful.

The Get More free templates were updated into 4 separate packs, earlier all templates were downloaded one at a time.
Now we can download 4 packs each being saved in separate folders containing loads of .exe files, each needs to be run to install the actual templates / samples.
Most if not all are saved to the VSPTemplate and VSPContent folders.
How many you have in these folders does depend on how far you got in installing the many .exe files.

Missing files of late include Text templates that install to X10 and DVD menu packs that are no where to be seen.

Running 2018 - 2019 - Get More - if you have already downloaded the packs they will have been moved into the My Library to the right instead of the main list.

As far as i see it
When i choose to download a free pack, say Graphics an .EXE file is downloaded and placed in the %temp% folder, once download is complete starts to install.
This creates a folder on our desktop containing the separate .exe templates, once complete the %temp% file is deleted. ( and should we interrupt the install we do have time to make a copy of the main .exe file)
Individual .exe files have to be run one at a time to install the templates or samples
For Graphics they are saved to the VSPContent folders

Which files are you particular bothered about?

[Davidk]

Adi,
I backed up the whole C drive before I started the upgrade. If it failed, there was a way back, that being to restore the prior the status quo by recovering the whole C Drive - windows 7 - image. But you've missed the point I have been making - this problem isn't about microsoft OS as such, but apparently the way installed versions of VS work with it. Every other software item I use has been fine under win10.

Trevor,
My interest was in relation to re-installed VS versions. Seemed no reason to download the extras again if they were already there. And your remark about VSPContent and VSPTemplate led me to a range of stuff in the Documents file tree in those folders. How do I install them? Or would it be easier just to download again?

[lata]

Hi David
All files within the VSPContents and VSPTemplate will populate libraries of Video Studio, they are common to all versions of video studio.
Saying that some more recent Instant Projects may struggle using with older versions.

But if they worked with W7 they should work now.

[Davidk]

Thanks Trevor. I think that means that any re-installed version will pick these up automatically.