Grimrock

The intel site had drivers 5 years out of date... somehow I think that might be a step in the wrong direction, the last version supported directly by Intel is for the 4th gen icore processors. We are talking about a first generation i3 core processor, not a 5th gen, just being replaced item...

The release of windows 10 saw Nvidia provide the whql drivers direct to Microsoft who then distributed them, apparently the deal was (at the time) that only Microsoft would provide these drivers but those poor individuals with GeForce experience installed ended up with a conflict as GE tried to automatically downgrade the drivers after the windows upgrade because the latest drivers weren't on Nvidia's website... stupid mistake and they sorted it quickly but only by listing the same driver as you get from MS.

I'm still a bit stumped as to how this mess came about - I did a complete clean install of the windows 10 insider preview and that worked - better than the release version...

jimbro1000 wrote:The intel site had drivers 5 years out of date... somehow I think that might be a step in the wrong direction, the last version supported directly by Intel is for the 4th gen icore processors. We are talking about a first generation i3 core processor, not a 5th gen, just being replaced item...

Well searching the Intel site is a bit of a pain but when i check their site i see the current drivers for 5th generation, dated juli 29th a.k.a. Win10 release date.

Regarding 1st gen i3 there are no Win10 drivers for the original Intel HD Graphics Adapter yet. The latest driver is for Win8 released 2 years ago. Looking at this Intel support thread i doubt there will be a driver for this chip in the future.

Its a bit off topic since you have the answer already from dr.disaster,

But why use win 10?. Is your win xp, win7, win8, or win8.1 broken? I think its not. Why update then? Don't fix that isn't broken.

Using the latest is bound you got probs with it. Stick to a stable OS.

trancelistic wrote:Its a bit off topic since you have the answer already from dr.disaster,

But why use win 10?. Is your win xp, win7, win8, or win8.1 broken? I think its not. Why update then? Don't fix that isn't broken.

Using the latest is bound you got probs with it. Stick to a stable OS.

**blink**
Would you prefer to go back to clay tablets perhaps? Is papyrus a bit too adventurous for you?

I've been running windows 10 for about 8 months in various pre-release versions and strangely didn't come across many problems. My laptop is the guinea pig in this - I also run a VM on my main workstation for parallel testing. It was only with the final release that it all went wrong.

If I was running win XP I'd be shooting myself for using a hideous OS that needed to be put down years ago but some fuddy-duddies couldn't cope with leaving it behind so it dragged its barely breathing carcass around for 5 long years before it got put out of everyone's misery. Vista is a joke and should never have been released. Windows 7 is workable but I'm past using it and only do so when forced. Windows 8 was actually quite likeable and 8.1 just that bit better although my laptop was already out of its comfort zone and as no windows 8 specific drivers were ever supplied for it by the manufacturer but I still got it all to work and better than it did with windows 7 thanks to better streamlining of the core.

Windows 10 is still a bit of an adventure but it is my job to keep ahead (quite literally) and if I can't do it at home and keep well informed I'd be poor at my job. Unfortunately there is an awful lot of rapid change in a lot of fields and I have to choose which bits to pay attention to - otherwise

So I've learned something new and perhaps found solutions for others to read up on when they hit the same problem. It still isn't properly fixed though - something LoG2 does when starting up really upsets the NVidia optimus system so it can't cope with the video switch from Intel to NVidia. Putting the laptop permanently into NVidia mode doesn't seem to make any odds and just causes other issues with applications trying to switch back to Intel which it really doesn't like.

Dr.Disaster wrote:

jimbro1000 wrote:The intel site had drivers 5 years out of date... somehow I think that might be a step in the wrong direction, the last version supported directly by Intel is for the 4th gen icore processors. We are talking about a first generation i3 core processor, not a 5th gen, just being replaced item...

Well searching the Intel site is a bit of a pain but when i check their site i see the current drivers for 5th generation, dated juli 29th a.k.a. Win10 release date.

Regarding 1st gen i3 there are no Win10 drivers for the original Intel HD Graphics Adapter yet. The latest driver is for Win8 released 2 years ago. Looking at this Intel support thread i doubt there will be a driver for this chip in the future.

The reason there aren't any new drivers is because Microsoft maintain them - over 50% of their PC customer base is using Intel and the vast majority are on iCore now so they have a vested interest in making sure the drivers work (shame they can't be a***d to fix the z-sort problem but that only affects a tiny percentage). Microsoft have been maintaining those drivers for years and yes I have searched the Intel website quite thoroughly on the subject. For most people the simplest solution to any problems like this is to slap a cheap amd/NVidia gpu into their machines and switch to a better quality of driver but laptop users typically don't have that luxury (I could upgrade the GPU on my laptop if I want to get technical but it would be major surgery).

jimbro1000 wrote:For most people the simplest solution to any problems like this is to slap a cheap amd/NVidia gpu into their machines and switch to a better quality of driver but laptop users typically don't have that luxury (I could upgrade the GPU on my laptop if I want to get technical but it would be major surgery).

nVidia offers only two drivers for their mobile gpu's: the regular one for GT 4xx M to current top model and the legacy one for all older gpu's. Is yours a GT 3xx M or even older?

Anyway, i found this list including minimum and recommended Win10 system requirements. Here the original Intel HD Graphics gpu and all nVidia gpu's before the 600 series are considered minimum requirement. That might result in some limitations.

Dr.Disaster wrote:

jimbro1000 wrote:For most people the simplest solution to any problems like this is to slap a cheap amd/NVidia gpu into their machines and switch to a better quality of driver but laptop users typically don't have that luxury (I could upgrade the GPU on my laptop if I want to get technical but it would be major surgery).

nVidia offers only two drivers for their mobile gpu's: the regular one for GT 4xx M to current top model and the legacy one for all older gpu's. Is yours a GT 3xx M or even older?

Anyway, i found this list including minimum and recommended Win10 system requirements. Here the original Intel HD Graphics gpu and all nVidia gpu's before the 600 series are considered minimum requirement. That might result in some limitations.

It is a 420m and that easily meets minimum requirements - I really think the problem here is the NVidia optimus graphics switcher. The differences between the 4xx and 6xx GPUs at the low end are pretty cosmetic performance wise.

Just a quick update. Two NVidia driver releases later and the problem appears resolved.
I am now running driver version 355.82 (released on August 31st), hopefully this will now stay fixed

Registered just to add this...

I wanted to add something to this since I was running into the exact same problem since upgrading to windows 10.

Windows 10 changes permissions in the Documents directory. I had to enable a registry hack to add a "take ownership" item to my menu when I right click on a directory.

Did that on the Almost Human directory under my documents and ... poof. The game runs.

Also had issues with deleting/writing saves with a few other games (Xcom, etc.) and this resolved that for me as well.

Hope this helps someone else.

YellowFive wrote:Windows 10 changes permissions in the Documents directory.

There is no change. The permissions are exactly the same in Win10 predecessors. The Document directory of a user can be accessed by the user this directory belongs to, the system user and the windows administrator group.

When you need to "take ownership" of a directory to access said directory it does either not belong to your user or he does not have admin rights. The easy way to solve this problem is to make your user an administrator.