"api-ms-win-downlevel..."

I am receiving an error when the system boots up and the windows GUI appear about 2 files, both starting with "api-ms-win-downlevel...". I've used a Win7 SP1 64 bits as source and I'm using the 82 version of winbuilder.

Hi fscussel,

These Api are not in original windows 7 SP1 source. I guess you have a  Windows 7 SP1 updated.
Perhaps you have IE10 integrated with prerequisite updates, including KB2670838 a platform update. 

If this is the case, it is not planned at this time. You need, for now, a Win7 Sp1 source without these updates.
For info, do you have Internet Explorer 8 selected in your build? Do you have the same error without this script?

http://originaldll.com/file/api-ms-win-downlevel-user32-l1-1-0.dll/35294.html

I see you met the same error I have.

I call him Dave. Because, I keep saying I can't do that Dave. calling regsvr and dumping a valid copy in a couple spots as described got rid of the error as stated in the link above.

http://originaldll.com/file/api-ms-win-downlevel-user32-l1-1-0.dll/35294.html

I see you met the same error I have.

I call him Dave. Because, I keep saying I can't do that Dave. calling regsvr and dumping a valid copy in a couple spots as described got rid of the error as stated in the link above.

Hi fscussel,

These Api are not in original windows 7 SP1 source. I guess you have a  Windows 7 SP1 updated.
Perhaps you have IE10 integrated with prerequisite updates, including KB2670838 a platform update. 

If this is the case, it is not planned at this time. You need, for now, a Win7 Sp1 source without these updates.
For info, do you have Internet Explorer 8 selected in your build? Do you have the same error without this script?

I am almost certain that the error is related to C++ redistributable package, not very sure which, but probably 2005 + 2012 (must have them both installed and the error probably will go away). Problem is there are many versions of those, and the application CAN require an older one, even you having the last one.

http://originaldll.com/file/api-ms-win-downlevel-user32-l1-1-0.dll/35294.html

I see you met the same error I have.

I call him Dave. Because, I keep saying I can't do that Dave. calling regsvr and dumping a valid copy in a couple spots as described got rid of the error as stated in the link above.

Hi fscussel,

These Api are not in original windows 7 SP1 source. I guess you have a  Windows 7 SP1 updated.
Perhaps you have IE10 integrated with prerequisite updates, including KB2670838 a platform update. 

If this is the case, it is not planned at this time. You need, for now, a Win7 Sp1 source without these updates.
For info, do you have Internet Explorer 8 selected in your build? Do you have the same error without this script?

I am almost certain that the error is related to C++ redistributable package, not very sure which, but probably 2005 + 2012 (must have them both installed and the error probably will go away). Problem is there are many versions of those, and the application CAN require an older one, even you having the last one.

aff couldn't find the EDIT post option, but forget what I've said before, I've messed up answers, the problem in the topic was probably related to me using the wrong version of Windows 7 as source, I'm not very sure but I believe I was using one with all the updates and must use a virgem one. As the staff suggested me. That fixed it.

aff couldn't find the EDIT post option, but forget what I've said before, I've messed up answers, the problem in the topic was probably related to me using the wrong version of Windows 7 as source, I'm not very sure but I believe I was using one with all the updates and must use a virgem one. As the staff suggested me. That fixed it.

I think you need 10 post to be able to edit, it is a spam protection.
Some updates seems to give some problems, difficult to know which of them or add controls.
In case of doubt, it is better to use an original and untouched Win7 SP0 or SP1

AARGH!  If that was the case, then one of my "bad result" builds with .Net 4.0 frame work might have actually worked. I just had updates installed that screwed the pooch.

Need a clown nose sound  to bleep me out. Thank God for closed doors to my office, now to plan on revisiting a few previous build attempts with a clean Win7SP1 disk.