My company still has a classic asp site that we are working to upgrade to .net. Our entire development team ground to a halt when we upgraded to windows feature 1803 which introduced task view. A single page went from a few seconds to over 8 minutes to load. Since classic asp and VBScript are not popular there was nothing about this on stack overflow.
I found the fix and wanted to leave this info here in case anyone else also is having this issue.
You need to get the vbscript.dll file from a pre-1803 feature branch of windows and copy it to your updated machine. I did this in two locations c:\windows\system32 and c:\windows\SysWOW64. Not sure if both were needed, but my page load time went from 8+minutes to under 10 seconds.
I recommend keeping your original dll just in case.
You will need to change the owner of the file from Trusted Installer to Administrators to grant yourself the permission to touch the file.
Related
I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.
I try to update my windows but I got this message:
I tried to reboot service but it didn't work.
Current version of my laptop: Version 1709 (OS Build 16299.192)
I am afraid this will be affected to future releases.
I recently had a similar problem on my PC and my laptop. My error code was as follows:
2018-08 Update for Windows 10 Version 1709 for x64-based Systems (KB4023057) - Error 0x80070643
After much kafuffle and reading quite a few articles and Microsoft waffle pages I decided to do it my own "straightforward" way. This is my story, if it helps you I am content. Summary:
Close/save all open applications;
Run Windows Update TroubleShooter;
Find the latest Cumulative Update;
Run the Cumulative Update;
Allow the computer to do the necessary restart processing.
The description below is what I did. It worked both times for me; firstly on my PC and secondly on my laptop. The difference with my laptop was that I didn't repeat the download of the Cumulative Update as I had already done this for the PC, I just ported the Update to the laptop via USB; everything else was the same.
On the laptop the whole process took about 40 minutes, start to finish. I didn't time it on my PC as I was doing things in slow stages. The download of the update is quite large (900Mb) so watch out for download charges if your ISP makes you pay for such things.
All descriptions/statements below apply solely to me. I am describing what I did and what I think. Like with Microsoft and others, any decision by you to follow any aspect of my description is entirely at your own risk. For any "lawyers" out there, any reference to "you" or implications that I am telling you what to do is just an unintended flaw in my poor English grammar.
Save and close all the applications that are being used:
The Cumulative Update will requires a restart of the computer so, for me, it was best to save any data now and close all the applications I had open in an orderly manner.
Find and run the Windows Update TroubleShooter:
Search the web for "Windows Update TroubleShooter". The page I ended up on was this:
https://support.microsoft.com/en-gb/help/4027322/windows-update-troubleshooter
Click the appropriate download link on this page. I am running Windows 10 (Version 1709; x64) so, for me it was: "Download Troubleshooter for Windows 10"; it was a small file, around 200Kb.
The download file was "wu170509.diagcab". I always "Save > Virus check > and then run".
Run the Troubleshooter (I double-clicked it);
On its first page, click "Advanced", then ensure "Apply repairs automatically" is checked, and finally click "Run as administrator". It reloads itself, click "Next" and let it run.
Whenever it found a problem I chose the "Apply this fix" option.
When it reports that it has completed, close the TroubleShooter.
This took me about 10 minutes to do (I am slow and I was also trying to make a cup of tea!).
Find the computer's details:
Load the Settings page; right-click the Windows "Start" icon -> Settings -> System -> About.
Note the following:
Under Device Specifications, note the System Type (mine is 64 bit "x64")
Under Windows Specifications, note the Edition, Version and OS Build details.
Find and run the Microsoft Update Catalogue:
Open a browser (mine is Internet Explorer) in Admin mode ("Run as Administrator" from its icon's Context Menu - I don't know why you have to do this but you get an error otherwise on IE);
Search the web for "Microsoft Update Catalogue"; the page I ended up on was this:
https://www.catalog.update.microsoft.com/home.aspx
Search for the latest Cumulative update for your version. I entered the following search terms that relate to my system in this year "2018 cumulative update windows 10 1709 x64";
Top of my returned list (the latest cumulative update) was:
2018-09 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4464217)
Note its KB number and click on its Title.
An "Update Details" window opens; click on the "More Information" link and a web page opens, mine was:
September 17, 2018—KB4464217 (OS Build 16299.666)
Verify the KB number with the Microsoft Catalog number just to make sure.
I only proceeded with this Update because its Build Number was greater than my current one (from section 3 above); for me, going backwards sounds like a route to a bigger mess.
Once I was content I was going forward I went back to the Microsoft Catalog (closing web pages and windows as necessary) and clicked the "Download" link for this Cumulative Update (KB4464217); a "Download" window appears. Click the link to download it (it says 863Mb). My download took 5 minutes via an Ethernet connection (no idea on timing regarding a WiFi download).
Run and check the Cumulative Update:
When the download had completed (and after virus checking it), I opened its folder and double-clicked the file therein and let it run. It took about 30 minutes to do its work. Once started it needed no help from me so I wandered off and did other work.
Once the Cumulative Update had completed I let it do its necessary restart. This is in fact a couple of restarts and took about another 10 minutes to complete.
Once these restarts had completed I loaded my system and did an immediate Windows Update. It returned with no errors and reported that my system was up to date - Yippee!
Notes:
A. There was one difference between updating my PC and laptop. On the PC my Desktop layout was undisturbed, on my laptop the Desktop layout was reset. I have no idea why the difference occurred.
B. In the middle of writing this, when I got to describing the Windows Update TroubleShooter, I decided to rerun the TroubleShooter on my PC. To my surprise it reported errors. I had done nothing of any significance since applying the Cumulative Update and checking it, just some simple Powershell stuff (Microsoft product) and a bit of internet browsing like news and football results (via Internet Explorer, another Microsoft product). It seems to me that Microsoft are screwing up their own Update System! What clever people they are - not.
Good Luck peoples - Pay It Forward.
The following Microsoft forum article suggests that it is a Windows Update glitch:
Update for Windows 10 Version 1709 for x64-based Systems (KB4041994) — error 0x80070643.
The article further suggests that the OP there has the later build of Windows, and that the problem may be suppressed by hiding the update (how-to provided in the linked article).
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
So I was one of the unlucky who didn't get the reservation on my PC despite meeting all the requriments.
Now I would like to update to win 10 using the MediaCreationTool by Microsoft.
My concert tho is, would updating the system this way be the same as with the reservation?
Meaning will I get to keep my files, and have the option to go back within 30 days?
I'm running win7 Home Premium x64 SP1
Will be glad for any answer
I've done it and I kept all my files and apps.
I also have Windows Rollback (The option to go back that u mentioned)
I was running win8.1 x64
The best option for me. Open the computer, remove the system Hard drive, and get an empty one installed in the PC or laptop, and then install the new Op System you want to try, do the drivers, updates, put some of your software, and test it for a while. If you don't like it, just change the H Disk for the old one.
We are experiencing a difficult problem which has been puzzling us for some time. We have two MSI setup files containing COM+ components and GUI respectively. The applications in both are written in VB6.
After a lot of testing we have arrived at this:
Application initially installed: Works.
Application uninstalled, new version installed: Does not work.
New application uninstalled, old application installed again (should work): Does not work.
The components are installed on Windows Vista clients, initially by Active Directory deployment, but testing is done by removing that deployment from AD, manually uninstalling and manually installing.
With “Does not work” I mean: Unable to complete a transaction. It seems to be a timeout on anything between 200 and 445 seconds. The GUI application is using the COM+ components to DTC to a server witch a MSSQL database.
Now why am I posting such a specific error? I'm looking for information regarding:
Any Windows Update update of MSDTC / COM+ the past year that could affect new installations.
This may be a common problem that others have a hint to what could be causing it.
Is there a COM+ cleanup utility to remove "old junk"?
Could this be a result of how Windows Vista handles the old "dll-hell" problem, that the new version introduces a new shared file?
Could it be something with versioning on components? (We have hundreds of them, difficult to say)
Ok, weird.
It seems installing SQL Native Client and opening for DTS in the local firewall solved the problem. The problem was actually that the SQLOLEDB provider seemed to break when reinstalling the application. This was not the case 1 year ago with the same executable, so something could have been changed on the network or by windows update.