Installing Win 7 problem

[LCF-AT]

Hi guys and Merry Christmas,

after few weeks I am back on internet a little.Since my last post 2 weeks ago my PC got broken because of any reason XY.Nothing was working anymore and my PC died (I think the mainboard was the problem).Really bad.Ok, the good news are I am using a new PC now but the bad news are I cant install my Win 7 x86 from my USB stick anyhow.Just get the message about CD/DVD driver etc.On internet I found a lot of infos and videos which do differ pretty much or less.Just read thats a missing USB 3.0 driver issue Win7 dosent have included into ISO image.Hhhmm.Great!I tried already some stuff I read but without success.Just tried to set all files on USB stick to write protected and just putting it into USB 2.0 port but all failed.Also disabled all 4 USB 3.1 ports but also failed.Just would like to know what I can do now to handle that problem without to start some big actions you know, maybe there is any simple quick solution for this.

I have this mainboard...

https://www.asus.com/Motherboards/PRIME-H310M-E-R2-0/

...something with UEFI schnick schnack etc.Many settings for many things you know.But I do stuck and come not go on yet because of that wonderful USB 3.x problem with Win 7.I need some help from you guys to get that issue managed anyhow and installing my Win7 from my USB stick with success.Can you help?Maybe this link below....

https://techlr.de/windows-7-installation-mit-usb-3-0-treibern/

http://codeabitwiser.com/2014/03/how-to-install-windows-7-with-only-usb-3-0-ports/

https://www.thomas-krenn.com/de/wiki/Windows_7_USB_3.0_Treiber_einbinden

...anyone tried something like that already in the past?

I cant do very much because I am using a old laptop to write this message.Simple solutions would be welcome in that case.So if you have ideas or tiny steplist etc then just post it please.Thanks.

Otherwise in the worse case (Wurst-Käse) I have to install Windows 10 64 anyhow (I dont have yet).

PS: Isnt it possible just to change some settings in the BIOS only to bypass this USB 3.x problem to make Win 7 installing work and enable it later again etc.

greetz

[atom0s]

Links like what you posted and things like this:

https://www.prime-expert.com/articles/b31/how-to-install-windows-7-from-usb-3-0/
https://www.poweriso.com/tutorials/install-windows-7-from-usb-3.0-port.htm
http://woshub.com/adding-usb-3-0-controller-drivers-to-windows-7-install-media/

 

All explain how to create proper bootable USB drives for USB 3.0. You can find the boards USB driver on their site as well for Win7 here:

https://www.asus.com/us/Motherboards/PRIME-H310M-E-R2-0/HelpDesk_Download/

[HostageOfCode]

Haven't faced this problem but would try first to install dos to c from usb and then copy the win7 installation to c and install from there.

Edited December 25, 2019 by HostageOfCode
Smylies

[sfs]

try using https://rufus.ie/    set gtp for uefi or mbr when creating usb boot  ,   for uefi to needs gtp partition  cheme

[LCF-AT]

Hi guys,

thanks for your answers so far.

I still dont know what to do.

1.) I dont see any USB drivers for my mainboard.Just some Bios cap file for win7 x86.

2.) I am using XP on laptop and rufus needs Win 7 or higher.

3.) Here is nothing to download...

https://downloadcenter.intel.com/product/65855

What now?

So I need a app to create a bootable USB for XP and a OS iso.If this Win7 dosent work anymore because of that USB issues then I have to install Win 10 x86 or x64 but I dont know whether I need a key for this on installing process or whether it has a test trial time etc and how to get a key.Also dont know which image of Win 10 I need to download.Maybe you have some infos for me for total noobs.

Thanks

[NOP]

Rufus states...

Quote

for Windows: XP/7/8/10 operating systems.

else you could try an old version

http://olddownload.com/rufus-usb/?windows=XP

 

[Progman]

There also exists the possibility to add a driver into a Win7 x86 image.  This can be done using dism.exe add-driver option after mounting the WIM file and so forth.  There are plenty of guides on this (not sure maybe the ones above).  If your USB controller is integrated into the motherboard which since you cannot find a driver it likely is.  Then you can just slipstream the whole chipset driver for the motherboard.  Somewhere in the chipset driver, there will be the USB 3.0 driver.  AFAIK, this is not a USB issue, but a Windows lacking a driver issue hence the route I mention.  Probably very similar to the guides above.  I have done this before with SCSI and RAID drivers and such and it has resolved any error messages when done correctly.  You can probably mount the WIM file right on the USB drive as well.  No need for rufus as if this is a Windows driver-level issue, the normal USB installer should be just fine.  Just slipstream the correct latest Win7 x86 chipset driver and off you go.

[Progman]

Note: a simple google search for "Intel LGA-1151 chipset driver" yields first result: https://downloadcenter.intel.com/product/90591/Intel-Z170-Chipset.  On that page is probably exactly what you want:  Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 8/9/100 Series and Intel® C220/C610 Chipset Family 
Installs Intel® USB 3.0 eXtensible Host Controller Driver (version 5.0.4.43v2) for Intel® 8 Series/C220 Series Chipset Families and 4th Generation Intel® Core™ Processor U-Series Platform.
Driver
Windows 7, 32-bit*
Windows 7, 64-bit*
Windows Server 2008 R2*
5.0.4.43v2
Latest
9/28/2018

Then go here: https://downloadcenter.intel.com/download/22824/Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-8-9-100-Series-and-Intel-C220-C610-Chipset-Family?product=90591

Then download your driver: https://downloadcenter.intel.com/downloads/eula/22824/Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-8-9-100-Series-and-Intel-C220-C610-Chipset-Family?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F22824%2Feng%2FIntel(R)_USB_3.0_eXtensible_Host_Controller_Driver_5.0.4.43_v2.zip

Then slipstream with dism after mounting the WIM file on the USB drive.  Boot off of it and install.  Hope it helps.

 

Oh and for more information on identifying your chipset since its probably not Z170 - but almost certainly uses the same drivers as Intel tries to bundle many chipsets into single drivers and that covers many series, but see here for more info: https://en.wikipedia.org/wiki/LGA_1151.  There are other ways in XP you can try to identify your chipset like CPU-Z, etc.  But ultimately Intel's driver site will have the right driver, if that was the wrong one then slipstreaming it simply won't have any effect when you try to install otherwise it will work perfectly as the hardware ID will be in the driver.

Also it could not hurt to make sure you have the v1007 BIOS driver as given in the ASUS link above.  Sometimes USB3 compatibility fixes are in those BIOS updates.  Always best to update BIOS first IMO.

Edited December 25, 2019 by Progman

[LCF-AT]

Hi guys,

thanks again for feedback.Those steps looking still complex to make it simple done for me.Are there no Win7 iso images to download which have already all those drivers?

Info: I installed Windows 10 home 32 bit at the moment and this was working / installing total quick from USB (only from USB 2.0 port working).Looks a little new now etc but it works so far to use my PC.Only problem I found is that my DVD rom dosent read DVDs!=?I tried to load the mainboard DVD into without success.Now I am not sure whether I still need to install something from that DVD like drivers for CPU chips and those stuff you know.In the device manager seems everything ok so far what makes me think that all drivers was installed already from that iso etc.No clue why my  DVD rom not works anymore and only normal CDs are working!?Hhmm.

Question: Maybe I should use Win 10 now so long it works (Trial) to see whether I can work with it good or not before I try to get back to Win 7.

Question2: Does anyone knows where I can see the rest trial days infos in Win 10?I dont know how long I can test it.Only thing I see is that I cant change some settings and see a watermark on the right screen corner.

Question3: Lets say I wanna use Win 10 so where should I get the right activation key from?On internet I found many source with diffrent prices also on amazon (many with bad feedbacks about key not working etc).A friend bought Win 10 in a store a while ago with box / manual / USB stick / Key.So can I use this key too for myself anyhow etc?Maybe you have some hints or experience about that you could tell.

greetz

[Progman]

See also here which has a tool helping avoid the command line stuff for exactly your issue: https://www.poweriso.com/tutorials/install-windows-7-from-usb-3.0-port.htm

Say your Win7 x86 USB stick is mounted as H: and your driver is unzipped at location C:\drivers with inf file mydriver.inf only something along the lines of these reasonably easy commands are needed:

mkdir c:\test

Dism /Mount-Image /ImageFile:H:\sources\boot.wim /MountDir:C:\test

Dism /Image:C:\test /Add-Driver /Driver:C:\drivers\mydriver.inf

Dism /Unmount-Image /MountDir:C:\test /Commit

rmdir /s /q c:\test

 

Note it is done on the boot.wim file and not install.wim.

Not sure if any prebuilt versions are out there but its quite easy to do really.

Its worth the experience to learn this anyway.

 

As for Win10, AFAIK, Microsoft had no time restrictions on the demo at least previously.

[atom0s]

CD Issues: Could be driver or codec based. Could also be regional related issues with locking and such.

Question: Maybe I should use Win 10 now so long it works (Trial) to see whether I can work with it good or not before I try to get back to Win 7.

Would be completely up to you and based on what you need/do with the OS. A lot of older tools that have any type of driver will not work without removing driver signing restrictions as well as not working in general due to the shifts in OS function offsets. So that may be a deal breaker if your focus is still on using older tools. (Ideally for that though you can just toss Win7 onto a VM and do any needed work there instead that requires those tools.)

Question2: Does anyone knows where I can see the rest trial days infos in Win 10?I dont know how long I can test it.Only thing I see is that I cant change some settings and see a watermark on the right screen corner.

Windows did away with the timer/lockdown setup they used to have in the older OS's. Instead, Windows 10 non-activated just has a handful of things disabled/restricted. It's more to deter usage for long periods of time as a main OS without being activated now. You can't do basic things such as changing the desktop wallpaper by normal means etc.

Question3: Lets say I wanna use Win 10 so where should I get the right activation key from?On internet I found many source with diffrent prices also on amazon (many with bad feedbacks about key not working etc).A friend bought Win 10 in a store a while ago with box / manual / USB stick / Key.So can I use this key too for myself anyhow etc?Maybe you have some hints or experience about that you could tell.

Getting keys from Microsoft directly are generally expensive. You can find OEM keys for fairly cheap though on sites like:
 - https://www.g2deal.com/windows-10-professional-new-deal.html
 - https://software-codes.com/products/windows-10-pro

There are also KMS servers around the web to activate leaked keys for free if you feel the need to go that route.

 

[Xjun]

download it. 

http://www.wepe.com.cn/

[LCF-AT]

Hi again,

thanks again for your infos so far.Ok, so that means I can use my actually Win 10 without to have fear that its one day no more working to access my desktop or internet etc right?I see I cant personalize some stuff at the moment but its ok at the moment during testing out Win 10.

About the keys.I am not sure whether I should choose a OEM key so I dont wanna be a slave of my used hardware you know.On the other hand a retail key is moer expensive (I have a retail key from my friend who using it - dont wanna use the same key yet to prevent that my friend cant use the key anymore etc).As  I said I am pretty unsure what to do at the moment.

New question about Windows 10 32 bit I am using at the moment.So my mainboard driver DVD dosent work to read it as I told before.Now I tried to download the driver from ASUS homepage....

https://www.asus.com/de/Motherboards/PRIME-H310M-E-R2-0/HelpDesk_Download/

...on choosing the OS I dont see a Windows 10 32 bit choice only 64 bit!=?Why this?Now I tried to choose a other OS without name to show drivers but they are also just for 64 bit systems!What a bullshit!Is this mainboard only designed for x64?I wanted to download the audio drivers but cant install them because I am using 32 bit OS.On internet I didnt found any driver...for 32 bit like this 64 bit...

Realtek Audio Driver V6.0.1.8504 for Windows 10 64-bit---(WHQL)

....I think I need to install any drivers for audio because the audio on Windows 10 is really BAD!No clue why.The sound does stutter every second and  the volume is getting up & down anyhow.Total ultra bad (I am using headphones).This is not normal and not same like I had on Win 7.I dont know what the problem is.Just think its the used driver from MS maybe.

Example: When I play a file with ADTS codec it does stutter + volume up / down problems.When I play a ACC codec file then it has only the volume issues.But all in all the sound sounds just strange and not normal.How to fix that problems now?I tried to change some settings in audio menus but without success.I just wanna have  normal stereo sound without any dolby or whatever you know.Maybe you can help with that problem I have too.Thanks.

greetz

[NOP]

There are 32bit drivers available HERE , are any of those compatible?

[atom0s]

...on choosing the OS I dont see a Windows 10 32 bit choice only 64 bit!=?Why this?

Driver manufacturers are lessing their load by no longer supporting platforms that are basically dead. Both Intel and AMD no longer create 32bit processors for the mainstream market. (Only for embedded systems and similar now.) So there isn't really a reason/means for manufacturers to continue making drivers for platforms they are not intended for or target with their hardware. In a lot of cases you'll see that hardware will specifically state it requires 64bit OS's now too, and not just software with that requirement. 

That isn't to say you can't find any 32bit versions of things though, there are manufacturer specific implementations of drivers to support said systems as well as older OS's but generally the hardware manufactuer isn't the one supporting it. There's also no guarantee using random drivers from other places will work even if its for the same purpose.

Would recommend you use 64bit Windows given that you have the hardware to support it.

[LCF-AT]

Hi again,

I installed new sound drivers.I think sound is ok now also the sound is a little too low.I do remember that I did changed the sound volume anyhow on Win 7 to make it louder but dont know anymore how I did that.I did fixed that delay stutter sound problem in VLC with changing the cache values.

Hhmm good ok, seems that all using or must use x64 OS these days.Not sure wheter I should choose the x64 Win version as my main OS.In this case I cant use my x32 apps anymore directly or just limited etc you know.

greetz

[atom0s]

Not sure if you realize this but 32bit apps run fine on 64bit systems. Windows, for example, has a layer built in to allow this all seamlessly. 

https://docs.microsoft.com/en-us/windows/win32/winprog64/running-32-bit-applications

Windows also has compatibility modes to help with running older apps that expect certain subsystems. (Win XP, Vista, 7 etc.)

The main reason you may run into issues with say, old unpacking related things is due to driver signing enforcement on newer Windows versions. You can either manually sign said drivers, or disable the enforcement if you absolutely need/want to run things that old. You can also run things in a VM if you need to still have an actual instance of an older 32bit OS running too.

[Progman]

64-bit is definetely advantageous almost no reason to use a 32-bit OS anymore besides some special driver issues as mentioned - compatibility, debugging and so forth.  64-bit can address more than 4GB RAM and native 64-bit apps can be faster than their 32-bit counterparts as obviously double the execution bandwidth for instructions operating on numeric data but not always as it depends on execution context.  But generally the smart approach is a 64-bit OS and all 64-bit apps and 32-bit apps where a 64-bit version is not available (for example Visual Studio for whatever reason has dragged their heals on a native 64-bit build with still no plans to port it despite numerous requests).  Oh, and also 64-bit OS allows the processor to use virtualization modes which can better support VMs.

Personally I find 32-bit assembly a lot more readable than 64-bit however.  But this is not an issue again unless dealing with driver-level stuff or in the case a 32-bit build is not available for an only 64-bit binary.

Edited December 30, 2019 by Progman

[LCF-AT]

Hi again guys,

32 bit apps running fine on 64 bit OS?Sounds new for me.If I remember right then people always told they have problems running 32 bit apps correctly etc on 64 bit OS.

Ok so I am still just testing Win 10 32 bit.If I understand you guys right then I should switch to 64 bit.Can I be sure that my 32 bit apps (Firewall etc) are also working then?I dont think so because its using also driver/s.What about my coding stuff (WinASM 32 bit), can I use this too as before to code 32 bit apps?Just wanna be sure about that so I dont wanna use / start each time a VM to run my apps or so, that was my main reason installing 32 bit OS instead of 64 bit you know.

Question: Lets I wanna install 64 OS now, so can I install it over the 32 bit OS without trouble and without to format the HDD?

PS: What can I get or do more with x64 compared to x86?I have access to more RAM (now I have 3 GB usable and waste 5 GB).Thats the only thing I know so far (dont have much clue about x64).Is there any big diffrent I can feel anyhow?

greetz

[NOP]

I code x32 and x64 apps all the time on my x64 system

I think you are maybe mixing up previous posts long time ago maybe on PE rebuilt incorrectly which didn't work on x64 systems. Olly x64 was pretty much dead and lots of scripts were still using x32 but things have moved on since...

All programs I have used for a long time x32 & x64 have worked flawlessly on my win10 x64 (and my old Win7 x64) and I use some apps daily which are x64 only

All the apps you mention should work no problem, having a 64 bit system will allow x64 apps to work more efficient especially combined with greater ram which you have with x64 

As others have said, if you do happen to have a really old app or script that requires x32 then just use a VM

BTW, in case you haven't used win10 before then look at disabling all the crappy telemetry that wasn't in Win7

😀

Edited December 30, 2019 by NOP

[LCF-AT]

Hi,

thanks for this infos again.So if I did know this before (32 apps run on 64 fine) then I had choosen the 64 bit installer OS.Great!I think in this case I have to install the OS again with 64 bit version.

About telemetry & co.I found many diffrent infos how to disable this or that like services but I didnt found some of them.Only DiagTrack I could disable.The others dmwappushservice /dmwappushsvc I cant find in services list.Maybe they are also renamed now.Maybe you can post later a actually list what to disable or change / add in registry.

I also tried already to disable this RuntimeBroker.exe which are running many times in processlist but all infos I found how to disable it failed.Maybe you have a info for this too to prevent starting this process.Thanks again.

Happy New Year guy.

[NOP]

2 hours ago, LCF-AT said:

Maybe you can post later a actually list what to disable or change / add in registry.

I use shutup10 and anti-beacon to disable telemetry

I have done a lot of service removal and reg tweaks in win10 in the past but cant remember which ones but if there's anything your stuck on removing then list them here

Only thing I don't like is cortana, it can be disabled but always running process but cant be removed easily without also affecting some functionality in win10

Also i disabled forced auto windows updates, this is not easy but also an option

😁

Edited December 31, 2019 by NOP

[Teddy Rogers]

If you want a trimmed down version of Windows 10 opt for running Windows 10 LTSC 2019, excerpt from Wikipedia...

Quote

This servicing option is exclusively available for Windows 10 Enterprise LTSC edition and distributes snapshots of this edition that are updated every 2-3 years. LTSC builds adhere to Microsoft's traditional support policy which was in effect before Windows 10: They are not updated with new features, and are supported with critical updates for 10 years after their release. Microsoft officially discourages the use of LTSC outside of "special-purpose devices" that perform a fixed function and thus do not require new user experience features. As a result, it excludes Windows Store, most Cortana functionality, and most bundled apps (including Microsoft Edge). According to a Microsoft announcement, this servicing option was renamed from Long-Term Servicing Branch (LTSB) in 2016 to Long-Term Servicing Channel (LTSC) in 2018, to match the name changes mentioned above.

Ted.

[LCF-AT]

Hi again,

short question about Win 10 again.Somehow I always get a exception when I run some of my apps (which using Exception Logger) the whole time.Also when I run any app in OllyDBG or x32dbg then I get this exceptions too in  a endless loop.They get handled and the apps running but the exceptions dosent stop.

EXCEPTION_DEBUG_INFO:
           dwFirstChance: 1
           ExceptionCode: E06D7363 (CPP_EH_EXCEPTION)
          ExceptionFlags: 00000001
        ExceptionAddress: 758F20D2 kernelbase.758F20D2
        NumberParameters: 3
ExceptionInformation[00]: 19930520
ExceptionInformation[01]: 0008E9FC
ExceptionInformation[02]: 73203F80 coremessaging.73203F80
First chance exception on 758F20D2 (E06D7363, CPP_EH_EXCEPTION)!

Has anyone a idea why this happens non stop etc?

greetz

[LCF-AT]

Hi again,

I checked that exception issue again and see that it happens into 2 dlls called....

C:\Windows\System32\CoreMessaging.dll
C:\Windows\System32\CoreUIComponents.dll

....throwing then the whole time.

0014ED6C   73453FBF  RETURN to CoreMess.73453FBF from <JMP.&msvcrt._CxxThrowException>
0014ED70   0014ED84
0014ED74   734A3F80  CoreMess.734A3F80
0014ED78   00762748  UNICODE "TextInputServer"

0014ED28   771DA768  /CALL to RaiseException from msvcrt.771DA762
0014ED2C   E06D7363  |ExceptionCode = E06D7363
0014ED30   00000001  |ExceptionFlags = EXCEPTION_NONCONTINUABLE
0014ED34   00000003  |nArguments = 3
0014ED38   0014ED5C  \pArguments = 0014ED5C

0014EEFC   71A8DC41  RETURN to CoreUICo.71A8DC41 from <JMP.&msvcrt._CxxThrowException>
0014EF00   0014EF14
0014EF04   71C2D8F0  CoreUICo.71C2D8F0
0014EF08   006F2078

0014EEB8   771DA768  /CALL to RaiseException from msvcrt.771DA762
0014EEBC   E06D7363  |ExceptionCode = E06D7363
0014EEC0   00000001  |ExceptionFlags = EXCEPTION_NONCONTINUABLE
0014EEC4   00000003  |nArguments = 3
0014EEC8   0014EEEC  \pArguments = 0014EEEC

ESI 771A3DA8 ASCII "Access violation - no RTTI data!"

So what is that?Is this normal producing that exceptions the whole time?Or is there something wrong?As I said it happens with any file I do load in debugger and run it.You can also load Olly in Olly etc.My log is printing the whole time....

75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
75C720D2   Exception E06D7363
etc

Can anyone check this out to see whether you get same issue on Win 10 32bit?

greetz