A505-6980 signed drivers

recently replaced hard drive on my a505-6980. used recovery discs to reinstall windows 7, all is working except that i am forced to use f8 when booting because windows 7 is not recognizing digital signature on drivers. i dumped and reloaded drivers straight from toshiba site without sucess. any ideas? thanx, zuppa

I have A505=6980 with window 7 64bit and replaced bad hard drive. I ended up downloading advanced format technoligy update for new hard drive then installed update for each individual piece of hardware that said it needed driver signing from Toshiba and everything worked except Network LAN connection, updated that driver from device manager. Everything works now.
Thank you for reporting your experience.
Others have said that installing the following new driver was sufficient. No need to reinstall drivers.
Intel Rapid Storage Technology
-Jerry

Similar Messages

Bulletin Board for A505-6980

Does anyone know how to find the Bulletin Board on a A505-6980? The advertisement for this machine says that the Bulletin Board in available on this machine but I cannot find in on the computer.

Satellite A505-S6980
Mystery to me. I don't see anything about it in the specs above.
And I don't see anything in the User's Guide.
Satellite A500 Series User’s Guide
More about it here.
Toshiba Bulletin Board
Let us know if you figure this one out.
-Jerry

Tried to install itune 10 but when i plug the iphone to the usb it states that it's not digitally signed drivers, i'm using window 7

tried to install itune 10 but when i plug the iphone to the USB it states that it's not digitally signed drivers, installation failed and cant even do charging on the computer after that. i'm using window 7 please help!!

Hello raks99,
The article linked below details a number of steps that can help with getting your iPhone restored via iTunes.
If you can't update or restore your iPhone, iPad, or iPod touch
http://support.apple.com/en-us/HT201263
Cheers,
Allen

XP SP1 and Signed drivers

Ever since I downloaded XP SP1 and re-installed some of the same drivers I had from MSI (vga/lan/sound) for my 845G Max L board, the drivers are no longer digitally signed. I think it has to do with something about HCT 10.0 and HCT 11.0. Does any know what is going on? Is MSI going to re-certify their drivers for HCT 11.0?
?(

As of Firefox 13.0 one needs at minimum Windows XP SP2. The last to work on SP1 was Firefox 12.0
http://www.mozilla.org/en-US/firefox/12.0/system-requirements/
http://www.mozilla.org/en-US/firefox/13.0/system-requirements/
http://www.mozilla.org/en-US/firefox/27.0/system-requirements/
edit: The last security update for Fx 3.6 was 3.6.28 and not 3.6.22

DVD recording on A505-6980

Is it possible to record a DVD on this model to another DVD, or how do we record to hard drive?

No CD/DVD drive can take a lot of bouncing around while operating as it can jar the read/write head out of place, which if it's in the process of burning can render the disk unusable. The same caution would apply to a desktop system as well, but few if those are likely to be moved while in use.

Looking for 2 signed drivers for Probook 470 G1

Ok, thanks, I'll try that. For now I tested the Ralink version 11.0.759.0 available at HP. Manually it installed well with command-line setup.exe /s /v"/qn LOGPATH=\"C:\BT_470G1.log\" REBOOT=Suppress /l*v \"C:\BluesoleilMsiInstall.log\" Now I'll see if it installs with SCCM. I'll post my findings

Hi: The only suggestion I can offer is to try each of the ones listed on the revision histor tab starting with the newest one. http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5405417&swItemId=ob_147890_1&swEnvOid=4059#tab-history

HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

Hello,
Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
this task, so I decided that I'd better share my experience here.
Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
Here's how you can do that.
1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
2. In the User Account Control window click Yes to confirm elevation of command shell.
3. At the command prompt type
bcdedit
to list your BCD entries.
This will give you an output like:
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
{a329b5ca-fb29-11e1-a74d-f2c962d62240}
{a329b5c2-fb29-11e1-a74d-f2c962d62240}
{current}
{a329b5d8-fb29-11e1-a74d-f2c962d62240}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8prowmc01.vhdx
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8prowmc01.vhdx
systemroot \Windows
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
boot menu.
The following record
default {current}
indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
Windows Boot Loader
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8prowmc01.vhdx
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8prowmc01.vhdx
systemroot \Windows
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
This record has a unique GUID identifier that can be used to reference this boot entry, which is:
identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
device vhd=[D:]\win8prowmc01.vhdx
And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
path \EFI\Microsoft\Boot\bootmgfw.efi
3. Now locate the current boot entry.
Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
look like:
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
This is done by running the following command:
C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
4. Make sure the entry has been successfully created.
Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
C:\Windows\system32>bcdedit
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
{a329b5cc-fb29-11e1-a74d-f2c962d62240}
{a329b5ca-fb29-11e1-a74d-f2c962d62240}
{a329b5c2-fb29-11e1-a74d-f2c962d62240}
{current}
{a329b5d8-fb29-11e1-a74d-f2c962d62240}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
5. Modify created No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
ons DISABLE_INTEGRITY_CHECKS
The operation completed successfully.
6. Verify that load option has been added.
Run the bcdedit command:
Windows Boot Loader
identifier {current}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description Windows 8 Enterprise RTM
locale en-US
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
7. Add the option that turns on test signing mode and disables checks of driver signature.
Adding the testsigning option and setting it to ON does the trick for us:
C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
We check it by running bcdedit:
Windows Boot Loader
identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
device vhd=[D:]\win8rtm.vhdx
path \Windows\system32\winload.efi
description No Driver Signature Check
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
integrityservices Enable
recoveryenabled Yes
testsigning Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice vhd=[D:]\win8rtm.vhdx
systemroot \Windows
resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
Hope this will help anybody to create their own custom boot configurations.
Well this is the world we live in And these are the hands we're given...

Hi,
Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions.
Regards,
Kelvin hsu
TechNet Community Support

W2K8 Server Shared Printers won't install if drivers not in Win7 C:\Windows\System32\DriverStore\FileRepository?

We have Windows 7 64 bit computers in two domains that just recently will not install printers (Windows 2008 R2 print servers) if the driver folder for the printer does not already exist in C:\Windows\System32\DriverStore\FileRepository. This
is under a domain administrator account logged onto the workstation.
If the driver folder exists then it will install but if the printer is brand new and doesn't use an existing driver or uses a new driver, the folder will not be populated in the FileRepository. For example if you rename the Lexmark Universal Printer Driver
folder lmud0c40.inf_amd64..... to another name and delete try to reinstall the same printer you had working 5 minutes earlier, it will not install. The C:\Windows\System32\Spool\Drivers\x64\3 folder STILL contains all the drivers for the printer
but for some reason it won't
The error is: Connect to Printer: Windows cannot connect to printer: Operation Failed with Error 0x00000057
All the "googled" solutions say to add the folder to the FileRepository manually but that is unrealistic with 19,000+ computers.
This exists across multiple domains, with multiple printer types and is not related to Group Policy as the issue still exists in a computer no policies applied except that had point and print=disabled. It also doesn't appear to be permissions based
as I granted the user "full control" of the FileDepository folder and it didn't make a difference.
They are signed drivers. The Print$ is shared on the server.
The odd thing is that in another domain we have, it works just fine even with regular user accounts (with point and print disabled). The server serves up the printer driver to the spool folder and it is copied to the FileRepository
lforbes

I was suggesting pkgmngr just to confirm on one machine that it could stage the package.
The package drivers are copied to the client from the PCC share on the print server
\\Server\print$\x64\pcc
The cab file is copied to client , extracted , then staged to the filerepository. At this point the spooler will install the print driver from the package and copy the file to the \system32\spool\drivers\x64\3 directory and loaded into the spooler
process from there.
For drivers that are not package aware, there is not a digital signature copied with the file set.
Package aware print drivers contain this data in the printer inf file
[PrinterPackageInstallation.amd64]
PackageAware=TRUE
The spooler does some secure validation using the asyncRPC protocols with package aware drivers and I've hit odd issues when stale machine accounts exist cross domain. I know you are not hitting this exact issue but verifing someone did not disable
the protocol in some domain policy (through reg entry) was the request.
Regarding the Point and Printer Restrictions policy. Disabling (or configuring) the policy disables the Restrictions around point and print. There is also server information that can be included in the policy. There are also another
policies to verify
Computer\Admin Templates\Printers\Only use Package Point and print
Computer\Admin Templates\Printers\Package Point and Print - approved servers
With Windows8 and Server 2012, the Version 4 drivers are loaded directly from the driverstore. Version 3 drivers still use the same path.
Hope that's not too much info.
Alan Morris Windows Printing Team
Thanks for the info:
So an update on this on the "fix" which really isn't a fix at all.
If you take Admin ownership of the C:\Windows\System32\DriverStore folder, set Admins=Full Control and delete the 4 added .dat files in there and then restart the print spooler service, you can add printers as an administrator.
Basically this defeats the entire purpose of adding printers to the FileRepository under the SYSTEM account.
It is at this point that it fails "The cab file is copied to client , extracted , then staged to the filerepository."
The drivers are digitally signed, in fact they are the "default" windows drivers from the default store.
I verified the driver cab files are in the
\\printserver\print$\x64\PCC folder
I did a test and this "fixed" it although it is not something we can implement.
If gave Administrators ownership of the C:\Windows\System32\DriverStore folder, set Admins=Full Control and deleted the 4 or 5 added .dat files in there I renamed the existing FileDespository to "old" and created a new one and then restarted
the print spooler service.
The printer had never been added before so it didn't exist in the registry.
On the restart of the spool service the folder a folder was created in the File Repository called
ntprint.inf_amd64_neutral_4616c3de1949be6d
Then on the install of the driver, by an administrator account, two more were created downloaded from the \\printserver\print$\x64\PCC
prnms001.inf_amd64_neutral_9fe8503f82cd60fa
prhp002.inf_amd64_neutral_04d05d1f6a90ea24 (printer driver)
So basically whatever gives SYSTEM access to "add" drivers to the DriverStore seems to be broken. It works OK if the Administrators have full control of all the files but not if it is running under SYSTEM.
I tried to disable the AsyncRPC protocol and then undid the disable. It didn't make a difference.
I have found hotfixes for Windows 7 Printer issues and have applied them all and the rollup and they didn't make a difference.
http://support.microsoft.com/kb/2647753
http://support.microsoft.com/default.aspx?scid=kb;en-US;2388142
KB982728
lforbes

WTF Creative fix winXP x64 driver new beta drivers still have the 4GB memory limit is

SBAX_PCDRVBETA_US_2_8_000.exe
I just pop in my audigy 2 ZS to see if beta drivers released June 8 fixed the no 5. issue with pass drivers unless u had no more then 4GB or limited the OS to 4GB using boot.ini
*no sound from my center and rear speakers
"the Known Issues:
* When using 5. Speaker configuration, no audio output from the Center/Rear channels.
?? To restore audio output in Windows XP: Launch Play Control Panel, click the Speaker Volume button, then click the Restore Defaults button."? (did not work no matter how many times i tried it's + also did numeros reboots)
doesn't work ? only after adding /MAXMEM=4096 did everything start working like it should.
my computer has 8GB of ram and by using this fix the other 4GB go to waste why is this issue fixed on Vista x64 drivers but NOT on XP x64
come on Creative WTF?:angry:
so creative nothing was fixed for WinXP x64 with this beta driver !!!!!!!!!!!
Message Edited by ATT-Half on 06-25-2008 07:8 AM

Re the F8 trick: Thanks. Still very annoying, as it needs to be pressed and selected on every boot. Still, it's a workaround. Re "hey it's only beta" and "not signed on purpose", I will argue that not signing drivers puts an unneccessary installation hurdle before the user. Worse, it is not readily apparent how to circumvent that hurdle. That drastically reduces the number of users that will install and use the driver, and could thus give feedback on it. My assumption is that Creative have released the beta drivers publically to get a wide range of good feedback on their performance. Also, to give the most impacted users an alternative to just removing their Creative card and falling back to onboard sound. Both objectives are more easily achieved if the driver can be installed - and used - without needing to go through an F8 boot menu on every startup. The driver is already designated as beta and carries a prominent expiration date. Not signing the driver does not do anything to alert the user of the fact that this is a beta that the expiration date popup did not already do. Look to graphics cards. You will find beta drivers there, released mainly to relieve pressing issues in-between driver releases. Those drivers are signed, yet no one doubts that they are beta drivers, not least because they are released on a page that displays a very prominent BETA logo. Creative has goals in publically releasing beta drivers, which won't be met if users can't install the drivers.

Msi drivers for gtx 280oc (177.42)

hello, what's the difference between msi 177.42 and nvidia 177.41? the reason i ask is these drivers are the only fully stable (including age of conan) drivers i can find. i tried both the latest signed drivers which seem to work better on some games (marginal frame rate increase which isnt needed) but don't work on other games at all, or have shocking problems. i havn't tried any of the older drivers from the msi site, or the 177?? from vista update. the nvidia forum and games forums all report similar problems to mine on newer drivers i just wondered what the difference was with the slight number change and non signed msi drivers.
many thanks.

over @ guru3d there's several newer drivers available some certifyed some betas , i'm using 180.10 rite now and for me it works great iq is up and so are frame rates
http://www.guru3d.com/
http://forums.guru3d.com/forumdisplay.php?f=21

Adding drivers to MDT that have no .inf file

I am currently creating images for a deployment server at work and have come across a problem. A few of the drivers I need to add, including the chipset driver, have no .inf files that I can see, I have extracted the .exe file using 7zip but this just produces
a number of random files. Can anyone help please??? I am using MDT 2013 and server 2012 essentials R2
Thanks

* You should only be using signed drivers in your environment.
* In order to get a *signed* driver from Microsoft, the IHV must supply a driver package that is installed via the *.inf file
* IHV's can add a *.exe wrapper after the fact, but the *.inf driver package is in there somewhere.
I have seen some instances of driver packages that have many working components that require a *.exe to install the individual *.inf parts in the correct order (some display drivers are like that), but these kind of drivers can be installed as an application
in the full OS. Any driver required to boot, should supply an *.inf package, if not please let us know so we can shame the IHV in question.
Additionally, some driver packages can be extracted without installation have you tried running the driver package with the /? switch to see if you can extract? or have you tried monitoring the %temp% directory to see what got created? Driver packaging
is an Art.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MSI StarCam Clip - signed driver for Windows 8

After upgrading to Windows 8 x64 I lost my webcam.
I tried install unsigned driver and camera worked for a while* (search for windows 8 install unsigned driver, I can't put one stupid link to post).
But after few days / restarts Windows decides to disable driver again.
Please can MSI release signed drivers for Windows 7 (32bit/64bit) and Windows 8?

Quote
Please can MSI release signed drivers for Windows 7 (32bit/64bit) and Windows 8?
Ask MSI: >>How to contact MSI.<<
This is a Users-to-Users Forum. Requests have to be pointed at MSI directly.

X200 Vista 64Bit Audio Drivers

I let System Update attempt to update the Connexant audio drivers and it failed because the update that was available was not signed. 64Bit requires all signed drivers. Now I can't even get back to how the machine originally shipped as the driver available for download appears to have the same issue.
Pointers to where I can find the right driver?

ChrisKinsman wrote:
Did you even read my post?
This isn't an issue with UAC. This isn't an issue with an ActiveX control and the authenticode prompt.
This is an issue with 64Bit Windows only loading signed drivers. Hvae you ever run a 64Bit OS?
EXCUSE ME?how do you expect to get an answer without reading your "COMPLETE" post? try following this method and the next time mind your language if you can!
go to cmd
2. Right-click on the shortcut and select Run as administrator
3. When the command window opens, type or paste the following and press ENTER:
Bcdedit.exe /set nointegritychecks ON
4. Reboot and then try installing the driver.
Message Edited by samavedam_vijay on 11-14-2008 08:44 PM
Message Edited by samavedam_vijay on 11-14-2008 08:45 PM
Message Edited by nonny on 11-14-2008 11:42 AM
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Lenovo U310: Clean Windows 7 Installation Guide (including Rapid Start and Caching)

Hi there,
this is the first time that I am writing such a guide/tutorial/whatever you may call it – there are probably better ones, but though not being a total computer noob, it took me almost one week to get this pretty (now again) little beast running again. So hopefully this helps some others to avoid such stupid downtimes.
A brief overview on what has happened to my original win 7 Home Premium:
As some may know, this laptop is very well usable as a “Hackintosh” called Macbook clone. So that’s what I did. It turned out to be nice, but I wanted to go back to Windows after a while, using a clean W7 Pro installation to start over. Actually an easy task, format all drives, install Windows, be happy. Just as I had been doing this for years. Unfortunately, it turned out to be a real challenge. First, I couldn’t “see” my drives during installation (and thus not install), then I got random errors during installation aborting it at different points and finally rapid start and caching didn’t work. Every time I tried to activate them (after Win installation), it crashed my PC. I even found an (official Lenovo!) guide stating to install W7 on the SSD, which worked, but sucks due to space limitations. Oh and another very nice thing: The SSD showed up during WIN installation (but not the classical hard drive) stating it was about 60 GB. So as you can see, I have had a lot of different tries and errors. Why I didn’t use Lenovo Easy Recover? As said before, I erased all partitions…
Before we start: If you have a good Windows running on the Laptop, do yourself a favor and disconnect the RAID 0 disks using the Intel Rapid Storage Application before(!!!) proceeding. It will make things much easier. And don’t forget to get all you data on an external drive or something.
Ok, now let’s start.
1.)    Prepare a USB Stick with the following driver
         http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21730 (choose f6flpy-x64.zip If you’re running a
         64-bit system (standard nowadays), take f6flpy-x86.zip if it is a 32-bit Windows, just download and copy them
         into the stick’s root directory) and plug this stick in one of the left side USB ports.
2.)    You’ll need Win 7 on either a DVD (plus external drive, for sure) or (bootable) USB stick
3.)    Connect your drive/stick (with W7) to the right side USB port.
4.)    Switch the computer on, immediately hit FN and F2. That will open the BIOS.
5.)    In the BIOS, navigate to the very right section (“save and exit”) and navigate the cursor to “load setup defaults”.
         Hit enter to approve.
6.)    After that, go to the “boot” tab and disable UEFI-boot.
7.)    Next, go one more tab to the left and set the controller setting to RAID (NOT AHCI or Compatible!!!).
8.)    Navigate the cursor down to “Intel Rapid Start” and hit enter. A submenu will pop up-
9.)    Disable the first entry in that window, that will make the rest be disabled as well.
10.) Navigate to the very right tab, this time hit save and exit.
11.) The PC restarts.
12.) Immediately hit FN and F12 to open the boot selection menu. Select to boot from your W7 DVD drive or USB
        stick.
13.) Click yourself through the whole process of installing Windows 7 until the page comes up where you will have
        to select where to install it.
14.) Click on “load drivers” and after a few seconds your downloaded driver should be there. Click ok to use them.
        Please do this step even if you can see your drives (SSD Disk 0, 32 GB and HDD Disk 1, 465(<-?) GB) as you
        would expect them – otherwise you’re very likely to get an error during the install process.
15.) Now erase all partitions on both drives and select the HDD as the drive to install W7 to – NOT THE SSD!!!!!
        Seriously, don’t choose the SSD.
16.) Windows will probably say that some extra partitions are necessary and so on, click ok and install Windows.
17.) After the installation has finished and you see your Desktop, I suggest you to proceed with the next steps in the
        following order to see as early as possible if you are on the right way.
18.) Install the Chipset driver, restart.
19.) Install the Intel Rapid Storage “driver” and check the box where it asks to additionally install the control center.
        Reboot.
20.) Go into BIOS (FN and F2) and enable Intel Rapid Start (the one you disabled in Step 8 and 9)
21.) Boot into Windows.
22.) Click on the Windows button, type cmd and right klick on the cmd.exe, select to run it as Admin.
23.) Now you’ll create a hibernation partition on the SSD. (which by now should be completely empty as we’ve
        deleted all partitions in step 15)
24.) In the command prompt that we have just opened, type: (without quotas, for sure)
“diskpart” and hit the enter button
“list disk” and hit the enter button
Now you should see your ssd as disk 0 and your hdd as disk 1
If your ssd is disk 0 (that would be standard), write “select disk 0”, otherwise write: “select disk 1”, and hit the enter button.
Now write “create partition primary size=4096” and hit enter again. [if you have 4GB of ram, type 4096, if you have 8 GB of ram, use 8192]
Now write “detail disk” and hit enter to see the volume number behind the volume that we have just created (it is 4 GB or 8 respectively, should be easy to find), in my case that was “2”
Now type “select volume 2” if your 4 or 8 GB volume has number 2 as well, otherwise use the number you found out in step f. Hit enter.
Finally, type: “set id=84 override” and hit enter for one last time.
It should now say back that the id has been set successfully.
Exit the command prompt. (close)
25.) Reboot
26.) Install the Rapid Start driver. Reboot.
27.) Open the Intel Rapid Storage Application.
28.) Click on accelerate and approve the settings. Two RAID’s will be created. Reboot.
29.) Install the remaining drivers, have fun with Windows Update and that’s it!
Good luck to all of you… And hey Lenovo - wouldn't that have been your job after all these posts showing your costumers in trouble? Just my two cents...
If you want, you can now turn on UEFI-boot in BIOS.
PS: If, after installing all drivers, you happen to see one unknown device in your device manager – this one belongs to Lenovo Connect Software that came with your Laptop. (Updates FB, Email etc when PC is in sleep mode) If you install Lenovo Connect it’s going to be fine, however, I would not recommend it as it is said to use a lot of energy and cause some other problems. So just live with it, your PC is totally fine without it.
Kind regards from Shanghai

Seriously guys, I can't use my 3 days old laptop. Some help would be mostly appreciated. At this point, the network connection issue doesn't show up anymore, it's just a blank screen after reboot. I reinstall windows and do it all over again just to achieve the same result.
Now couple of things caught my attention: as I load the "6flpy-x64.zip" driver from step 14, I get a message saying I need to install signed drivers, because unsigned ones are likely to mess up the system.
Secondly, I could not find any Rapid Storage Technology drivers for Windows 7 (particularly for U310 model), so I use the Windows 8 ones (http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031455), which seems a silly thing, yet I know of no alternatives.
Could it be any of these issues to cause my problem? Or smth else? Please help!

Split x2 - Touchpad issue after upgrading to Windows 8.1

Hello,
I bought this Split x 2 a week ago and it came with WIndows 8. Everything was working fine until I upgraded to WIndows 8.1. Now my Touchpad will freeze some times and I have to log out and log back in to my profile to unfreeze the touchpad other times I can get it to unfreeze by resetting the release touch screen buttom.
I called HP customer service and they said it was a Microsoft issue and transfer me to them. Microsoft said it was a hardware (HP) Issue and that i needed to go back to the store where I bought it
(BestBuy). I took it back yesterday to BestBuy and they gave me a knew one. I did the same thing and upgraded to Windows 8.1 and touchpad issues is back. So pretty sure is not a hardware issue.
All windows updates are completed
I checked the Touchpad's Driver and it is up to date.
NOTE: I plugged a wireless mouse to my laptop and when the touchpad freezes the wireless mouse still works.
Does anyone know a fix for this issue? Everything else works great on the laptop is just very inconvenient when you are working and you have to log out to get your touchpat to work again.
Any help would be appreaciate it.
Jhon C
This question was solved.
View Solution.

Well you gave me a great idea. So the same thing happened to me, the install failed due to the driver signature. I uninstalled the current driver, then turned off the feature that requires signed drivers and installed the driver. Everything is working so far.... the only odd thing is it doesn't show the driver any where. I am going to try a few other things BUT the mouse hasn't stopped working for a good half hour.
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-s... Incase you didn't know.

A505-6980 signed drivers

Similar Messages

Maybe you are looking for