If you haven't resolved this:
You would want to start by resolving your issues the CheckSur log.
You have it kinda easy; you have the same error from the same folder.
Repair methodology on: CSI Payload File Missing
CSI Payload File Missing means you are missing a payload file from your WinSxS folder. To resolve you'll need to identify, find and replace the files missing in their respective folder.
The error is (f) CSI Payload File Missing 0x00000000 <Payload File> <Payload Folder>
Payload Folder is the folder inside WinSXS, and the Payload File is the actual file missing.
In your case, all your CSI Payload File Missing errors are from same folder: amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7600.17107_none_66ff46fd953e6c5c
So with first error, you'd need to find replace api-ms-win-core-util-l1-1-0.dll with a good copy into the c:\windows\winsxs\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7600.17107_none_66ff46fd953e6c5c\
6.1.7600 is Windows 7 Base image, so you'd need to get the replacement copy from: 1) Another working Windows 7 SP0 (Starter, HB, HP, Pro, Ult: doesn't matter), 2) from your recovery partition WIM if PC with recovery partition, or 3) the install.wim from base Windows 7 SP0 install disk (can download legally online).
Once you have your good source, you'd just go through and replace each file missing.
After that, I'd run CheckSUR again to ensure all errors are handled; then attempt SP1 install via Standalone again.
Now, I imagine that SP1 will still fail with same error code, 0x80070490; because that specific error has it's own repair method.
After you get CheckSUR fixed. Attempt SP1 again, wait for fail and post up the CBS.log and go from there.
EDIT:
To expand:
0x80070490 means ELEMENT_NOT_FOUND; which is simply stating that an element should exist that isn't found. That element could very well be the files in winsxs that CheckSUR reports as missing, it could be files missing in another Windows Update, or it could be a corrupted driver in driver store.
If we continue to have the element not found after fixing checksur; then we'd look in CBS.log for 490 to identify a KB# causing SP1 to fail. In that case, we'd simply uninstall that update.
If we don't find a KB# reported in CBS log, we'd look in the setupapi.dev.log for 490 and uninstall that driver from driver store via pnputil -a
