WINDOWS 10: Installing Win10 with MediaCreationToolx64 and keeping files - windows-7

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.

Related

VBSCRIPT slow under Windows Feature Update 1803

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.

Cannot Install Oculus - Not Enough Disk Space

This post pertains to attempts to install the Oculus software (which is required for development with the Rift) that fail because there's not enough disk space when there in fact is. A little research reveals that this has been a problem since the DK1 and has to do with dynamic disks and the way Oculus installer attempts to ensure that the drive is fast enough.
https://forums.oculusvr.com/community/discussion/34739/oculussetup-exe-says-not-enough-space-when-space-exists/p1
I hesitated to post this on Stack Overflow, however, I encounter this error when trying to setup a Dev machine for VR development with Oculus, and the solution is sufficiently obscure and not available in a single location yet, and I felt overall it makes sense for it to be here.
You can try going the route of creating a VHD on your dynamic disk, however, for me, even after doing that, the Oculus installer wasn't able to recognize a drive to install on.
I was in a position to reinstall Windows 10. So, with a USB made with the latest Windows 10 installer, my drives were identified as dynamic and GPT and while I could reformat them I couldn't delete them or otherwise change them from dynamic using the GUI.
What worked for me was to go to the command prompt during Windows 10 installation (Shift-F10) and use "diskpart" command line utility to select the appropriate disk and clean it. Like so:
>> diskpart
>> select disk <disk#>
>> clean
>> exit
Then I was able to really format the drive through the Windows 10 installation GUI and proceed as usual with the installation of Windows 10 and then Oculus.

System Registry Error VB6 running as User Windows 10

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.

The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll

I am using "Microsoft Visual Studio" to work with an "MFC application".
I am using "Installshield" to create the setup file for this application.
I get a "setup.exe" file.
If I run this setup on a "Windows XP 32 bit" machine, the installation ends properly.
Yet, when I try to start the installed program, I get the message:
"The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll."
In debug mode, I can't find the moment the error occurs because whatever the breakpoint I put in the code, the message appears before reaching the breakpoint, I guess at the very beginning of the program execution...
Note: It works for Vista 32 bit and Seven 64 bit.
It appears lots of people do have the same problem but I couldn't find a solution for myself.
Can you help?
Thank you.
Welcome to the world of DLL hell and application dependency analysis.
I found that DLL on my Win8 machine in the SYSWOW64 (32bit System32 folder ) with version 7.0.9200.16384. Looking at it using Dependency Walker I can see it in fact exports the function you are looking for.
I also see on my InstallShield machine a merge module called MSVCRT.MSM that redistributes version 6.00.8797.0 of this file. However when I look it using Dependency Walker, I see it has the exported functions _except_handler2 and _except_handler_3 but not _except_handler_4_common.
So therefore you need a newer DLL and that merge module won't help you. Microsoft used to have this cool website called DLL Help Database that told you all the versions of a file and what shipped them but sadly they killed it.
BTW, I can also see that this DLL is installed with Windows these days. Windows XP? I'm not so sure as I'd have to fire up a VM and look.
A couple possible resolutions:
Find out what SP or Hotfix of Windows fixes this and make it a dependency of your MSI.
Grab the DLL from a Win 8 machine and add it to your INSTALLDIR and deploy it privately.
One final note. This is either caused by the version of Windows XP comes with an old version of the DLL ( A related KB Article says it does ) or that a third party application whacked the DLL causing the problem. Some more study is required here.
I recommend you first try installing the MSVC Redist version 2008. That one does include the implementation of the missing function.
This post is old but I wanted to leave my solution since this problem was hell to me. My python app was working for Linux, Win7, 8 and 10 but WinXP refused to work with that message.
I was using py2exe to get an executable and it will put some DLLs along with the exe file.
Deleting some dlls from the exe's directory was the only thing that make the app work in XP and continue working in the other systems:
[ "POWRPROF.dll","IPHLPAPI.DLL","USP10.DLL", "DNSAPI.DLL" ]
Also distributing "Microsoft.VC90.CRT" directory along with the exe file, with it's manifest and DLL files.
I hope this will be useful for someone, since it took me weeks to figure it out.
(i know the OP wasn't working with python, but the error is just the same)
Your program has a dependency which is not being satisfied on Windows XP. You might try using Dependency Walker to identify it, or you might check for known limitations. For example, Visual Studio 2012 doesn't support Windows XP until update 1 and a build option change - is that what you're using?
The problem was probably because you might used a corrupted DirectX version on your Win XP. It happened to me as well because I randomly downloaded a DirectX setup which was corrupted and caused these. The solution I did was is I deleted all the files that has anything to do with directX from C:Windows/System32, deleted the directX from add/remove program as well and completely removed the whole registry key from regedit. Local_machine/software/microsoft/DirectX... What I did then was found a original values and keys for DirectX 9 on the net and made a new registry key.
The DirectX folder was once completely and originally back on regedit and it showed in dxdiag that the directX is installed.
In case you encounter crashes in the game, I suggest you to download .NET Framework 3.5 Service Pack 1 and then make a backup on your PC (If you're not using nVIDIA graphic cards like I do, I use ATI Radeon) and download nVIDIA PhysX system software driver and see if it works. (You need nVIDIA phydX drivers to run this game without crashes only if you use Win XP, the problem shouldnt encounter on Win 7) In case the drivers screw up your PC (The nVIDIA PhysX one) you will be able to restore your old PC function before those drivers (If you made a backup of your PC, I suggest using Acronis Boot for backups) it means you're totally out of luck if you're not able to get the nVIDIA PhysX on ur for example, ATI graphics on Windows XP, because without nvidia physx, on Win XP, Metro wont run, while on Win 7 / Vista / 8 it should.
I just installed the latest VS 2017 and was running into the same problem. I googled everything but couldn't find any solution, so I just defined it myself:
extern "C" int _except_handler4_common() {
return 0; // whatever, I don't know what this is
}
I've spent the last 8 hours picking my code apart with this exact same error and it turned out to be a line of code in my application, specifically a check for IPv6 support in the OS:
conf.IPv6Disabled = !(Socket.OSSupportsIPv6);
I commented that line out and voila, error disappeared.
This problem persists to every software or game that requires windows 7 or 8 or vista but is made run into windows xp. So if you want to resume or start your program you need to upgrade your windows to 7 or 8 or vista as per the system requirements of the program.
HOPE IT WAS HELPFUL
THANKS

TortoiseSVN made my windows stop working soon after log in

I'm running an Windows 7 Home Basic in a Megaware machine with 8GB RAM, intel Core i5 2.9 GHz (x64), 1 TB of Hard Disk.
The problem is: since today, when i tried to update a project from an SVN repository at google code with TortoiseSVN 1.7.1 (for 64-bit systems) at the same time i opened the Eclipse (Indigo for Java EE), the windows just stops working. No error messages, i just can't do nothing. I can still move my mouse, but all the functions of the windows simply do not respond (i tried ctrl+alt+del , alt+f4, win, win+e, win+r...). I'm acessing via safe mode (with network).
I tried also to uninstall the Tortoise (had to find out how to turn on the MSIServer on), but even after uninstalling it, the problem continues. Can the Tortoise have damaged one of my system's file? Reinstall the windows is my last option, btw.
It might have, but I doubt it. It could also be something else that's been installed since then. Instead of reinstalling windows, go into your Start Menu, and select "System Restore". If you have a restore point defined from before you started experiencing problems, that could be a good way to get back to what you had without a full reinstall.

Resources