Apart from the solution mentioned in the link included in your question, here are a few other things you may want to try:
Temporary change the configuration of the file system used by Drupal, to use a relative path to the temp folder (eg ..\temp) instead of a full path (eg C:\path\to\your\webroot\temp).
In your question it says "... during the update of some modules...", but nowhere you explained HOW you're performing this update. Are you using the update tool within Drupal? Are you using Drush? Are you performing this update using FTP or something like that? Whichever method you use, try to use any of the other typical approaches for updating modules. While doing so, you may run into some other unexpected problem/message, which may actually give you a clue about what your real problem is. E.g. some problem with a tmp-like folder to just unpack the new version of the module.
Try to disable all your modules first, then re-enable one of them again, and apply all updates, if any, related to that module you just enabled. If for this first module the error doesn't come back, you've reduced the list of modules that cause your proble with one. If the error does come back, disable that module again (to be investigated in more detail afterwards). Repeat for each of your other modules. This approach should help you to find/identify the problem module (and either leave that disabled, or start in depth debugging of that module).