[ANSWERED] Problem with EX-100 v0.5.x.x Using Logitech/Portable Apps

Yes, download with media tool, but, without autounattend (if matters)...

Edit: Something's happened ... I have to realize...

Hello "KrX"  I solved the problem but do not know the cause ...
After several tests, without success, I changed the keyboard ... and everything works normally with all wccf file

ok nice that is it working now.

which changed your Keyboard, do you mean Hardware or did you Change the Keyboard layout?

Another keyboard wired... Only mouse is wireless, but it works

hmm ok. still its odd that it is working now;)

KrX wrote:

hmm ok. still its odd that it is working now;)

Finally i understood ... Drivers that are in Boot, Should not be in the folder Install...
                 Yesterday I made a new ISO and everything goes perfect!   
           You should do a preset for Desktop...     As you have done for Laptop. I think many members would enjoy... Especialy I!
                                                                                                       Have a nice day. 
                                                                                                                          Ruby

I skipped a few releases but now with Ex100_v0.7.1.0 everything is working again, do you know the Winterstorm or anyone know why it's all working again where as before it wasn't?

Caddict wrote:

I skipped a few releases but now with Ex100_v0.7.1.0 everything is working again, do you know the Winterstorm or anyone know why it's all working again where as before it wasn't?

isnt that the solution?

ruby2hora wrote:

KrX wrote:

hmm ok. still its odd that it is working now;)

Finally i understood ... Drivers that are in Boot, Should not be in the folder Install...

or maybe you are using another build? before i.e TH1 or TH2 and now Redstone ?

it seems MS changed a couple of things from TH2 to redstone, i get Errors and Problems in redstone which arent Happening with TH2

"isnt that the solution?

you are a funny guy, yes it did solve the problem, but i just thought if some one know actually why so that I can solve the problem quicker in the future if it happens again, instead of waiting for future releases.

Caddict wrote:

"isnt that the solution?

you are a funny guy,

yes i am xD

yes it did solve the problem, but i just thought if some one know actually why so that I can solve the problem quicker in the future if it happens again, instead of waiting for future releases.

i really cant say why, because i dont get such an problem so i could test it. maybe a keyboard layout caused it or a driver.

and if it is solved now it could be that winter fixed it by updating some components